Part Number Hot Search : 
FSAV330M ISL43485 A1733 LC75700 600ETT SC8560 DT54F L1010
Product Description
Full Text Search
 

To Download SAP51D-A-G1-T Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
  as - interface spec. v3.0 compliant universal as - i ic sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 1 january 28, 2016 brief description the sap5s/sap51 is a next - generation cmos inte - grated circuit for as - interface networks. this low - level field bus as - i (actuator sensor interface) was designed for easy, safe, and cost - effective inter - connection of sensors, actuators, and switches. it transports both power and data over the same two - wire unshielded cable. the sap5s/sap51 is used as part of a master or slave node and functions as an interface to the p hysical bus. it provides the power supply, physical data transfer, and communication protocol handling. the sap5s/sap51 is fully compliant with the as- interface complete specification v3.0 . it is func - tion and pin compatible with the sap4.1 (as2702). the s ap5s/sap51 can be programmed by the user to operate in standard slave mode, safety mode (sap5s only), or master mode. the special as - i safety mode (sap5s only) assures short response times regarding security - related events. all configuration data are store d in an internal eeprom that can be easily programmed by a sta - tionary or handheld programming device. the sap5s/sap51 is optimized for harsh environ - ments by its special burst protection circuitry and excellent electromagnetic compatibility. features ? comp liant with the as - interface complete specification v3.0 ? universal application: slaves, masters, repeaters ? integrated safety code generator (sap5s only) ? on - chip electronic inductor: 55ma current drive capability ? two led outputs to support all as - interfac e complete specification v3.0 status indication modes ? user programmable to operation in standard slave mode, safety mode, or master mode ? supports 5.33 and 16 mhz crystals by automatic frequency detection ? data pre - processing functions ? clock and communi cation watchdogs for high system security benefits ? cost savings due to integrated safety code generator (sap5s only ) ? special burst protection circuitry ? excellent electromagnetic compatibility physical characteristics ? operational temperature range: - 25 to +85c ? sop16 and sop 20 package available support ? idt as- interface programmer kit usb ? idt sap 5 evaluation board v2.0 related products ? asi4u universal as - interface ic sap5s/sap51 basic application circuits +24v +0v asi+ asi- asi+ asi- sap5s u5r cdc ltpn ltgp osc2 osc1 uout d2 d0 d1 d3 standard application safety mode slave application sap51/ sap5s u5r cdc ltpn ltgp osc2 osc1 uout dstbn led2 led1 pstbn p[3:0] d[3:0] pfault
as - interface spec. v3.0 compliant universal as - i ic sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 2 january 28, 2016 neg main state machine power supply pos man uart ltgp ltgn cdc u 5 r p [ 3 : 0 ] d [ 3 : 0 ] output led 1 , led 2 i / o dstbn output pstbn input pfault dstb led pstb pfault eeprom osc 1 osc 2 clk c l k o scillator pll c l k offset i / o offset i / o param data uout thermal protection apf power fail detector receiver transmitter electronic inductor typical applications ? as- i master modules ? as- i slave modules ? as- i safety modules (sap5s only) sap5 s/ sap51 block diagram ordering information ordering code operating temperature package type rohs? packaging sap5sd - a - g1 - t - 25c to +85c sop20 / 300 mil yes tubes (37 parts/tube) sap51d - a - g1 - t sap5sd - a - g1 - r - 25c to +85c sop20 / 300 mil yes tape and reel (1000 parts/reel) sap51d - a - g1 - r sap5sd - b - g1 - t - 25c to +85c sop16 / 300 mil yes tubes (46 parts/tube) sap51d - b - g1 - t sap5sd - b - g1 - r - 25c to +85c sop16 / 300 mil yes tape and reel (1000 parts/reel) sap51d - b - g1 - r corporate headquarters 6024 silver creek valley road san jose, ca 95138 www.idt.com sales 1- 800- 345- 7015 or 408- 284- 8200 fax: 408 - 284- 2775 www.idt.com/go/sales tech support www.idt.com/go/support disclaimer integrated device technology, inc. (idt) reserves the right to modify the products and/or specifications described herein at any time, without notice, at idt's sole discretion. performance specifications and operating parameters of the described products are determined in an independent state and are not guarante ed t o perform the same way when installed in customer products. the information contained herein is provided without representation or warranty of any kind, whether express or implied, includin g, but not limited to, the suitability of idt's products for any pa rticular purpose, an implied warranty of merchantability, or non - infringement of the intellectual property rights of others. this document is presented only as a guide and does not convey an y license under intellectual property rights of idt or any third p arties. idt's products are not intended for use in applications involving extreme environmental conditions or in life support systems or similar devices where the failure or malfunction of an idt product can be reasonably expected to significantly affect the health or safety of users. anyone using an idt product in such a manner does so at their own risk, absent an express, wri tten agreement by idt. integrated device technology, idt and the idt logo are trademarks or registered trademarks of idt and its s ubsidiaries in the united states and other countries. other trademarks used herein are the property of idt or their respective third party owners. for datasheet type definitions and a glossary of common terms, visit www.idt.com/go/glossary . all contents of this document are copyright of integrated device technology, inc. all rights reserved.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 3 january 28, 2016 contents 1 please read this first ...................................................................................................................................... 7 1.1. important notice ........................................................................................................................................ 7 1.2. silicon revision history ............................................................................................................................. 7 2 g eneral device specification ........................................................................................................................... 8 2.1. absolute maximum ratings (non - operating) ............................................................................................ 8 2.2. operating conditions ................................................................................................................................. 9 2.3. emc behavior ............................................................................................................................................ 9 2.4. quality standards .................................................................................................................................... 10 2.5. f ailure rate ............................................................................................................................................. 10 2.6. humidity class ......................................................................................................................................... 10 3 basic functional description .......................................................................................................................... 11 3.1. functional block diagram ........................................................................................................................ 11 3.2. general operational modes .................................................................................................................... 13 3.2.1. slave mode ....................................................................................................................................... 14 3.2.2. as- i communication channel ........................................................................................................... 14 3.2.3. parameter port pins .......................................................................................................................... 14 3. 2.4. data port pins ................................................................................................................................... 14 3.2.5. data input inversion .......................................................................................................................... 15 3.2.6. data input filtering ............................................................................................................................ 15 3.2.7. synchronous data i/o mode ............................................................................................................. 15 3.2.8. 4 input / 4 output processing in extended address mode ............................................................... 15 3.2.9. as- i safety mode .............................................................................................................................. 16 3.2.10. enhanced led status indication ...................................................................................................... 16 3.2.11. communication monitor/watchdog ................................................................................................... 16 3.2.12. write protection of id_code_extension_1 ....................................................................................... 16 3.2.13. summary of master calls .................................................................................................................. 17 4 eeprom ........................................................................................................................................................ 20 4.1. overview .................................................................................................................................................. 20 4.2. user area programming .......................................................................................................................... 21 4.3. firmware area programming .................................................................................................................. 23 4.4. safety area programming (sap5s only) ................................................................................................ 24 5 detailed functional description ...................................................................................................................... 26 5.1. power supply ........................................................................................................................................... 26 5.1.1. voltage output pins uout and u5r ................................................................................................ 26 5.1.2. input impedance (as - interface bus load) ....................................................................................... 27 5.2. thermal protection .................................................................................................................................. 28 5.3. dc characteristics ? digital inputs .......................................................................................................... 28
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 4 january 28, 2016 5.4. dc characteristics ? digital outputs ....................................................................................................... 29 5.5. as- i receiver ........................................................................................................................................... 29 5.6. as- i transmitter ....................................................................................................................................... 30 5.7. parameter port and pstbn ..................................................................................................................... 30 5.8. data port and dstbn .............................................................................................................................. 32 5.8. 1. timing of data i/o and dstbn ......................................................................................................... 32 5.8.2. input data pre - processing ................................................................................................................ 32 5.8.3. synchronous data i/o mode ............................................................................................................. 34 5.8.4. support of 4i/4o signaling in extended address mode ................................................................... 36 5.8.5. special function of dstbn ............................................................................................................... 38 5.9. data and parameter port configuration .................................................................................................. 38 5.10. fault indication input pfault ................................................................................................................ 39 5.11. led outputs ............................................................................................................................................ 40 5.11.1. slave mode ....................................................................................................................................... 40 5.11.2. master/repeater mode ..................................................................................................................... 41 5.12. oscillator pins osc1 and osc2 ............................................................................................................. 41 5.13. sap5 reset ............................................................................................................................................. 41 5.13.1. power - on reset ................................................................................................................................ 42 5.13.2. logic controlled reset ...................................................................................................................... 43 5.13.3. external reset ................................................................................................................................... 43 5.14. uart ....................................................................................................................................................... 43 5.15. main state machine ................................................................................................................................. 45 5.16. status registers ...................................................................................................................................... 45 5.17. communication monitor/watchdog ......................................................................................................... 46 5.18. safety mode (sap5s only) ...................................................................................................................... 47 5.19. master and repeater modes ................................................................................................................... 50 5.19.1. master/ repeater mode activation .................................................................................................... 50 5.19.2. pin assignment in master and repeater modes .............................................................................. 51 5.19.3. functional description ...................................................................................................................... 52 5.20. write protection of id_code_extension_1 .............................................................................................. 55 6 application circuits ......................................................................................................................................... 57 7 package specifications .................................................................................................................................. 60 7.1. package pin assignment ......................................................................................................................... 60 7.2. sop16 (300 mil) package outline ........................................................................................................... 62 7.3. sop20 (300 mil) package outline ........................................................................................................... 63 7.4. package marking ..................................................................................................................................... 64 8 ordering information ...................................................................................................................................... 65 9 related documents ........................................................................................................................................ 65
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 5 january 28, 2016 9.1. related idt documents .......................................................................................................................... 65 9.2. related third - party documents .............................................................................................................. 6 5 10 glossary ......................................................................................................................................................... 66 11 document revision history ............................................................................................................................ 66 list of figures figure 3.1 functional block diagram ................................................................................................................. 11 figure 3.2 data path in master and repeater modes ....................................................................................... 14 figure 5.1 basic receiver comparator threshold set - up principles ................................................................ 30 figure 5.2 timing diagram for parameter port p[3:0], pstbn .......................................................................... 31 figure 5.3 timing diagram for data port d[3:0] and dstbn ............................................................................. 32 figure 5.4 principles of delay mode input filtering ? example for slave with address 1 hex ............................ 33 figure 5.5 power - on behavior (all modes) ........................................................................................................ 42 figure 5.6 timing diagram external reset via dstbn ..................................................................................... 43 figure 5.7 safety mode data processing .......................................................................................................... 49 figure 5.8 data input voltage constraints in safety mode ................................................................................ 50 figure 5.9 sap package pin assignment in master/repeater mode ................................................................ 51 figure 6.1 standard application circuit, direction of data i/o depends on io_code ....................................... 57 figure 6.2 safety mode application ................................................................................................................... 58 figure 6.3 sap5 master mode applicatio n ........................................................................................................ 59 figure 7.1 sap51/sap5s sop20 package pin assignment ............................................................................ 61 figure 7.2 sap51 / sap5s sop16 package pin assignment .......................................................................... 61 figure 7.3 sop16 package outline dimensions ............................................................................................... 62 figure 7.4 sop20 package outline dimensions ............................................................................................... 63 figure 7.5 package marking 20 - pin version ..................................................................................................... 64 figure 7.6 package marking 16 - pin version ..................................................................................................... 64 list of tables table 2.1 absolute maximum ratings ................................................................................................................ 8 table 2.2 operating conditions .......................................................................................................................... 9 table 2.3 crystal frequency ............................................................................................................................... 9 table 3.1 assignment of operational modes .................................................................................................... 13 table 3.2 sap5 master calls and related slave responses .......................................................................... 18
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 6 january 28, 2016 table 3.3 sap5 additional master calls for slave configuration ..................................................................... 19 table 4.1 eeprom read and write times ..................................................................................................... 20 table 4.2 sap5 eeprom ? user and firmware area content ....................................................................... 21 table 4.3 sap5 eeprom ? user and firmware area programming .............................................................. 23 table 4.4 sap5 eeprom ? safety area content ............................................................................................ 24 table 5.1 properties of voltage output pins uout and u5r .......................................................................... 26 table 5.2 as- interface bus load properties .................................................................................................... 27 table 5.3 cdc pi n parameters ........................................................................................................................ 27 table 5.4 cut - off temperature ......................................................................................................................... 28 table 5.5 dc characteristics of digital high voltage input pins ...................................................................... 28 table 5.6 dc characteristics of digital high voltage output pins ................................................................... 29 table 5.7 receiver parameters ........................................................................................................................ 29 table 5.8 transmitter current amplitude .......................................................................................................... 30 table 5.9 timing for parameter ports ............................................................................................................... 31 table 5.10 timing for data port outp uts ............................................................................................................ 32 table 5.11 activation of delay mode .................................................................................................................. 33 table 5.12 activation of the synchronous data i/o mode .................................................................................. 34 table 5.13 meaning of master call bits i[3:0] with ext_addr_4i/4o_mode = ?1? ................................................ 37 table 5.14 data and parameter port configuration for non - safety - mode operation ........................................ 38 table 5.15 data and parameter port configuration in safety mode .................................................................. 39 table 5.16 led status indication ....................................................................................................................... 40 table 5.17 oscillator pin parameters ................................................................................................................. 41 table 5.18 sap5 initialization times .................................................................................................................. 42 table 5.19 power - on reset (por) threshold voltages .................................................................................... 42 table 5.20 timing of external reset .................................................................................................................. 43 table 5.21 status register content .................................................................................................................... 45 table 5.22 activation of the sap5 communication watchdog ........................................................................... 46 table 5.23 example for cryptographic code table ........................................................................................... 48 table 5.24 activation of the sap5 master/repeater mode ................................................................................ 51 table 5.25 sap5 pin assignment in master and repeater modes .................................................................... 51 table 5.26 functional differences between sap5 master and repeater modes .............................................. 52 table 5.27 programmable variation of the loopback time ............................................................................... 53 table 5.28 master/repeater mode parameter ................................................................................................... 54 table 5.29 write protection of id_code_extension_1 ....................................................................................... 56 table 7.1 sap51/sap5s package pin list ...................................................................................................... 60 table 7.2 sop16 package dimensions (mm) .................................................................................................. 62 table 7.3 sop20 package dimensions (mm) .................................................................................................. 63
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 7 january 28, 2016 1 please read this first 1.1. important notice important safety notice: this idt product is intended for use in commercial applications. applications requiring extended temperature range, unusual environmental requirements, or high reliability applications, such as military, medical life - support, or life - sustaining equipment, are spec ifically not recommended without additional mutually agreed upon processing by idt for such applications. 1.2. silicon revision history revision date technical changes affected page in datasheet b september 2005 first marketed silicon version . c march 2007 modified i il ? current range for input low level . table 5.5 on page 28 c march 2007 modified delay mode activation through parameter port p1 . page 33 c march 2007 modified synchronous data i/o mode activation through parameter port p2 . page 35 c march 2007 modified watchdog activation through parameter port p0 . page 46 c march 2007 improved b urst protection filter and improved esd behavior . d august 2012 uart d esign c orre c tions for end_bit t ransmission e rror d etection . improved as-i telegram pause detection . !
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 8 january 28, 2016 2 g eneral device specification important note : the absolute maximum ratings given in section 2.1 are stress ratings only. the sap5 might not function or be operable above the recommended operating conditions given in section 2.2 . stresses exceeding the absolute maximum ratings might also damage the device. in addition, extended exposure to stresses above the recommended operating conditions might affect device reliability. idt d oes not recommend designing to the specifications given under ?absolute maximum ratings.? important note : the operating conditions given in section 2.2 set the conditions over which idt specifies device operation. these are the conditions that the application circuit should provide to the device for it to function as intended. unless otherwise noted, the limits for parameters that appear in the o perating conditions section are used as test conditions. 2.1. absolute maximum ratings (non - o perating) table 2 . 1 absolute maximum ratings parameter symbol min max unit voltage reference v ltgn 0 0 v voltage difference 1) between ltgp and ltgn pins (v ltgp - v ltgn ) v ltgp - ltgn 0 40 v pulse voltage 2) , 3) between ltgp and ltgn (v ltgp - v ltgn ) v ltgp - ltgn_p 0 50 v voltage at the cdc, d0 , d1, d2, d3, p0 , p1, p2, p3, dstbn, pstbn, led1, led2, pfault, and uout pins v inputs1 - 0.3 v uout + 0.3 v voltage at the osc1, osc2, u5r pins v inputs2 - 0.3 7 v input current into any pin except supply pins 4) i in -50 50 ma humidity ? non - condensing 5) h electrostatic discharge 6) ? human body model (hbm2) v hbm 1500 v electrostatic discharge 7) ? equipment discharge model (edm) v edm 200 v storage temperature t stg -55 125 c soldering temperature sn/pb 8) t lead 240 c soldering temperature 100%sn 8) t lead 260 c thermal resistance of sop 16 package 9) r thj - 16 80 100 k/w thermal resistance of sop 20 package 9) r thj - 20 75 95 k/w 1) reverse polarity protection must be performed externally. 2) v ltgp - ltgn and v ltgp - ltgn_p must not be violated. 3) pulse with 50s, repetition rate 0.5 hz. 4) latch - up resistance , reference pin is 0v. 5) level 4 according to jedec - 020d is guaranteed. 6) hbm: c = 100pf charged to vhbm2 with resistor r = 1.5k ? in series, valid for all pins except ltgp - ltgn. 7) edm: c = 200pf charged to vedm with no resistor in series, valid for ltgp - ltgn only. 8) soldering must comply with the jedec - j- std - 020d standard. 9) single layer board, p tot = 0.5w; air velocity = 0m/s ? max. value; air velocity = 2.5m/s ? min. value.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 9 january 28, 2016 2.2. operating conditions table 2 . 2 operating conditions parameter symbol conditions min max. unit negative supply voltage v ltgn 0 0 v dc voltage at ltgp pin 1) , 2) v ltgp relative to v ltgn 16 34 v operating current i ltgp v ltgp = 30v f c = 16.000mhz n o load at any pin ; transmitter is turned off ; digital state machine is in idle state. 6 ma max. output sink current at pins d[3:0], dstbn i cl1 10 ma max. output sink current at pins p[3:0], pstbn i cl2 10 ma ambient operating temperature range t amb -25 85 c 1) below v ltgpmin the power supply block might not be able to provide the specified output currents at uout and u5r. 2) outside of these limits , the send current shape and send current amplitude cannot be guaranteed. table 2 . 3 crystal frequency parameter symbol conditions nominal unit crystal frequency 1) f c 5.333 or 16.000 mhz 1) the sap5 automatically detects whether the crystal frequency is 5.333mhz or 16.000mhz and controls the internal clock circuit accordingly. 2.3. emc behavior the sap51/sap5s fulfill s the requirements defined in as- interface complete specification v 3 . 0 and related test requirements for as- interface s lave ics. in addition to the as - interface complete specification and in combination with a reference component circuit , the sap51/sap5s achieve s a communication failure rate less than 10% of the allowed failure rate according to the "fast transient" test method specified in the related as- interface association test procedures. the behavior specified above is correct by de sign and is proven during sap51/sap5s characterization.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 10 january 28, 2016 2.4. quality standards the quality of the sap51/sap5s will be ensured according to the idt quality standards. idt is a qualified supplier according to iso/ts 16949:2002 and iso 14001:1996. the fol lowing idt reference documents apply for the development process (available on request; see section 9 ) : ? management regulation: 0410 product development p rocedure ? process specification: idt c7d 0.6m technology functional device parameters are valid for the device operating conditions spe cified in section 2.2 . production device tests are performed within the recommended ranges of v ltgp - v ltgn , t amb = +25c (+85c and - 25c on sampl e bas is only) unless otherwise stated. 2.5. failure rate symbol parameter max. unit aql acceptance quality level 0.1 % f55 failure rate at 55c 18 fit f70 failure rate at 70c 60 fit f85 failure rate at 85c 150 fit f125 failure rate at 125c 1400 fit 2.6. humidity class level 3 humidity tolerance according to jedec - 020d is guaranteed.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 11 january 28, 2016 3 basic functional description note: unless otherwise noted, the product name sap5 refers to both the sap51 and the sap5s. the sap5 is a low - level field bus ic designed for as - i (actuator sensor interface), which provides a secure interconnection for sensors, actuators, and switches via a two - wire unshielded cable. the sap5 is used as part of a master or slave node and functions as an interface to the physical bus. it provides the power supply, physical data transfer, and communication protocol handling. the sap5 can be programmed by the user to operate in standard slave mode, safety mode (sap5s only), or master mode. the special as - i safety mode (sap5s only) assures short respo nse times regarding security - related events. configuration data are stored in a programmable internal eeprom. the sap5 is optimized for harsh environments by its special burst protection circuitry and excellent electro - magnetic compatibility. 3.1. functional bl ock diagram figure 3 . 1 functional block diagram neg main state machine power supply pos man uart ltgp ltgn cdc u 5 r p [ 3 : 0 ] d [ 3 : 0 ] output led 1 , led 2 i / o dstbn output pstbn input pfault dstb led pstb pfault eeprom osc 1 osc 2 clk c l k o scillator pll c l k offset i / o offset i / o param data uout thermal protection apf power fail detector receiver transmitter electronic inductor
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 12 january 28, 2016 following device functions are handled by the different blocks of the sap5 : receiver the receive block converts the analog telegram waveform from the as-i bus to a digital pulse - coded signal that can be processed further by a digital uart circuit. the receive block is directly connected to the as- i line pins ltgp and ltgn. it converts the differenti al as-i telegram to a single - ended signal and removes the dc offset by high- pass filtering. to adapt quickly to changing signal amplitudes in telegrams from different network users, the amplitude of the first te legram pulse is measured by a 3 - bit flash adc and the threshold of a positive and a negative comparator is set accordingly to about 50% of the measured level. the comparators generate the p_pulse and n_pulse signals. transmitter the transmit block transforms a digital response signal to a correctly shaped send current signal , which is applied to the as-i bus. due to the inductive network behavior of the network , the changing send current induces voltage pulses on the network line that overlay the dc operating voltage. the voltage pulses must have si n2 - wave shapes ; therefore the send current shape must follow the integral of the sin2 - wave function. uart / main state machine / eeprom ee prom write access and other i/o operations of the main state machine are supported in slave mode only (see the description of the general sap5 operational mo des below). in master mode, the sap5 is basically equivalent to a physical layer transceiver. if slave mode is activated, the uart demodulates the received telegrams, verifies telegram syntax and timing , and co ntrols a register interface to the main state machine. after reception of a correct telegram, the uart generates appropriate receive strobe signals , which tell the main state machine to start further processing. the main state machine decodes the telegram information and starts respective i/o processes or eeprom access. a second register interface is used to send data back to the uart for construction of a telegram response. the uart modulates the response data into a manchester -ii- coded bit stream that is used to control the transmitter unit. electronic inductor the electronic inductor is basically a gyrator circuit. it provides an inductive behavior between the sap5 pins ltgp and uout while the inductance is controlled by the capacitor on the cdc pin . the inductor decouples the power regulator of the sap5 as well as the external load circuit from the as-i bus and hence prevents cross talk or switching noise from disturbing the telegram communication on the bus. the as- interface complete specification descri bes the input impedance behavior of a slave module via an equivalent circuit that consists of r, l , and c in parallel. for example, a slave module in extended address mode must have r > 13.5 k ? , l > 13.5 mh , and c < 50pf. the electronic inductor of the sap5 delivers values that are well within the required ranges for output currents up to 55ma (v ltgp >24v). more detailed parameters can be found in section 5.1 . the electronic inductor requires an external capacitor of 10f at the uout pin for stability. power supply the power supply block consists of a band - gap referenced 5v - regulator as well as other reverence voltage and bias current generators for internal use. the 5v regulator requires an external capacitor at pin u5r of at least 100nf for stability. it can source up to 4ma for external use, however the power dissipation and the resulting devi ce heating become a major concern if too much current is drawn from the regulator. see section 5.1 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 13 january 28, 2016 oscillator / pll the oscillator sup ports direct connection of 5.33 3 mhz or 16.000 mhz crystals with a dedicated load capacity of 12pf and parasitic pin capacities of up to 8pf. the sap5 automatically detects the oscillation frequency of the connected crystal and controls the internal clock generator circu it accordingly. after power - on reset , the sap5 is set to 16.000 mhz operation by default. after about 200s , it will either switch t o 5.333 mhz operation or remain in the 16.000 mhz mode. the frequency detection is active until the first as-i telegram has be en successfully received in order to en sure the sap5 has found the correct clock frequency setting. the detection result is locked thereafter to increase resistance against burst or other interferences. the oscillator unit also contains a clock watch dog circuit that can generate an unconditioned sap5 reset if there has been no clock oscillation for more than approximately 20s. this is to prevent unpredicted sap5 behavior if the clock signal is lost . thermal protection the sap5 is self - protected agai nst thermal overload. if the silicon die temperature rises above approximately 140c for more than 2 seconds, the sap5 detects thermal overheating, switches off the electronic inductor, performs an sap5 reset , and sets all analog blocks to power - down mode. the 5v r egulator is a lso turned off in this state; however, there will still remain a voltage of approximately 3 to 3.5 v available at u5r that is derived from the internal start circuitry. if the over - temperature condition is no longer present, the sap5 resumes operation and performs an initialization. power fail detector the power fail detector observes the voltage at the as-i line. it signals at the pstbn/apf pin when the voltage drops below approximately 22.5v. this is a ctive in master mode only. in put stage all digital inputs, except the oscillator pins, have high voltage capabilities and pull - up features. for more details see sections 5.3 , 5.7 , 5.8 and 7.1 . output stage al l digital output stages, except the oscillator pins, have high voltage capabilities and are implemented as nmos open - drain buffers. each pin can sink up to 10ma of current. see section 5.4 . 3.2. general operational modes the sap5 provides two operational modes: slave mode and master/repeater mode. the operational mode that becomes active is defined by programming the flag master_mode in the firmware area of the eeprom ( also see table 4 . 2 ). the eeprom is read out at every initialization of the sap5 . online mode switching is not provided. the configurations in table 3 . 1 apply: table 3 . 1 assignment of o perational m odes selected operational mode master mode flag slave mode 0 master/repeater mode 1 in slave mode , the sap5 operates as a fully featured as - i s lave ic according to as - interface complete specification v3.0 . in master/repeater mode , the sap5 acts as physical layer transceiver. it translates a digital output signal from the external master control logic ( e.g., programmable logic controller ( plc ) , microprocessor , etc. ) to a correctly shaped, analog as- i pulse sequence and vice versa. e very as- i telegram received is checked for consistency with the as - i communication protocol specifications and if no errors were found, an appropriate receive strobe signal is generated.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 14 january 28, 2016 figure 3 . 2 shows the different data path configurations. figure 3 . 2 data p ath in master and repeater mode s master m ode slave mode, as - i channel more detailed sign al descriptions can be found in section s 5.19 and 5.14 . 3.2.1. slave mode the slave mode is the most complex operational mode of the sap 5 . the sap5 support s not only all mandatory as- i s lave functions but also a variety of additional features that facilitate the design of as- i s lave modules. 3.2.2. as - i c ommunication c hannel the as- i channel is directly connected to the as- i b us via the pins ltgp and ltgn. a receiver and a transmitter unit are connected in parallel to the pins , which allow s fully bi - directional communication through ltgp and ltgn. 3.2.3. parameter port pins in the 20 - pin package , the sap5 features a 4 - bit wide parameter port (p0, p1, p2, and p3 pins) and a related parameter strobe signal pin pstbn. as- interface complete specification v3.0 newly defines a bidirectional mode for parameter data. the sap5 supports this feature , which can be activated by special eeprom setting ( io_code , see se ction 5.9 ). there is a defined phase relation between a parameter output event, the parameter input sampling , and the activation of the pstbn signal. th erefore it can be used to tr igger external logic or a micro controller to process the received parameter data or to provide new input data for the as - i s lave response. see section 5.7 for further details. 3.2.4. data port pins the sap5 provides a 4 - bit wide data port. the outputs work independently from each other allowing a maximum of 4 output devices to be connected to the sap5. the directions of the data port pins are set through the io_code , see section 5.9 . as- i receiver as- i transmitter cmos input led output uart asi+ asi - d0 (tx) led1 (rx)
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 15 january 28, 2016 the data port is accompanied by the data strobe signal dstbn. there is a defined phase relation between a data output event, the input data sampling and the activation of the dstbn signal. th us, it can be used to trigger e xternal logic or a micro controller to process the received data or to provide new input data for the as - i slave response. see section 5.8 for further details. 3.2.5. data input inversion by default , the logic signal (high / low) that is present at the data input pins during the input sampling phase is transferred without modification to the send register, which is interfaced by th e uart. thus , the signal becomes directly part of the slave response. some applications work with inverted logic levels. to avoid additional external inverters, the input signal can be inverted by the sap5 before transferring it to the send register. the inversion of the input signals can be done jointly for all data input p ins. see section 5.8 . 3.2.6. data input filtering to prevent input signal bouncing from being transferred to the as - i m aster, the data input signals can be digitally filtered. activation of the filter is done jointly either by eeprom configuration or by the logic state of parameter port pin p2. for more detailed information , refer to section 5.8 . 3.2.7. synchronous data i/o mode as- interface complete specification v3.0 newly defines a synchronous data i/o feature, which allows a number of slaves in the network to switch their outputs at the same time and to hav e their inputs sampled simultaneously. this feature is especially useful if more than 4 - bit wide data is to be provided synchronously to an application. the synchronization point i s defined as the data exchange event of the slave with the lowest address in the network. this definition relies on the cyclical slave polling with increasing slave addresses per cycle , which is one of the basic communication principles of as - i . the sap5 always monito rs the data communication and detects the change from a higher to a lower slave address. if such a change has been recognized, the sap5 assumes that the slave with the lower address has the lowest address in the network. there are some special procedures t hat become active during the start of synchronous i/o mode operation and if more than three consecutive telegrams have been sent to the same slave address. this is described in more detail in section 5.8.3 . 3.2.8. 4 input / 4 output p rocessing in extended address mode a new feature of as - interface complete specification v3.0 is additional support of 4 - bit wide output data in extended address mode. until as - int erface complete specification v2.11 , it was only possible to send three data output bits from the master to the slave in extended address mode because telegram bit i3 wa s used to select between the a or b slave type for extended slave addressing (up to 62 slaves per network). in normal address mode , bit i3 carries output data for pin d3.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 16 january 28, 2016 the new definition introdu ces a multiplexed data transfer so that all 4 - bits of the data output port can be used again. a first as - i cycle transfers the data for a 2 - bit o utput nibble only, and then the second as - i cycle transfers the data for the complementary 2 - bit nibble. nibble selection is done by the remaining third bit. to ensure continuous alternation of information bit i2 and thus continued data transfer of both nibbles, a special watchdog has been implemented that observes the state of the i2 bit. the watchdog can be activated or deactivated by eeprom setting. it provides a watchdog filter time of about 327ms. the multiplexed transfer increases the refresh time per output by a factor of two ; however, some applications can tolerate this increase and gain the advantage of less external circuitry and better slave address efficiency. the sampling cycle of the data inputs remains unchanged since the meaning of b it i3 has not been changed in the slave response with the definition of the extended address mode. more detailed information is given in section 5.8.4 . 3.2.9. as - i safety mode using the sap5 safety mode makes it easy to implement a safety - related as- i slave according to the as- i safety at work concept. slaves complying with the control category 4 according to en 954 ? 1 can be implemented even with a minimum of external circuitry. in safety mode , the respon se of the sap5 on a data_exchange master call ( dexg ) is different. instead of responding with the regular input data provided at the data ports, a 4 - bit data word from a specific 8 ? 4 bit code table is trans mitted to the master. cycling the code table is used to transmit another data word with each dexg master call. the data transmission is supervised by a s afety m onitor. in safety mode , the use of the enhanced d ata input features described in sections 3.2.5 to 3.2.8 are disabled. in this c ase , the s afety m ode related inputs act as 3 - level inputs. see section 5.18 for further details. 3.2.10. enhanced led status indication the sap5 supports stat us indication by two led outputs. more detailed information on the signaling scheme can be found in section 5.11 . 3.2.11. communication monitor/watchdog data and p arameter communication is continuously observed by a communication monitor. if neither data_exchange nor write_parameter calls have been addressed to and received by the sap5 within a time frame of a pproximately 41ms, the no data/parameter exchange s tatus is detected and signaled at led1. if the respective flags are set in the eeprom , the communication monitor can also act as a communication watchdog that initiates a complete sap5 reset after the expiration of the watchdog timer. the watchdog mode can also be activated and deactivated by a signal at parameter port pin p0. for additional detailed information , see section 5.17 . 3.2.12. write p rotection of id_code_extension_1 as defined in as - interface complete specification v3.0 the sap5 also supports write protection for id_code_exten sion_1 . the feature allows the activation of new manufacturer - protected slave pro files and is enabled by eeprom setting. it is described in more detail in section 5.20 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 17 january 28, 2016 3.2.13. summary of master calls table 3 . 2 and table 3 . 3 on the following pages show the complete set of master calls that are decoded by the sap5 in slave mode. the master calls in table 3 . 3 are intended for programming the sap5 by the slave manufacturer only. they become deactivated as soon as the lock_ee_prg and safety_program_mode_disable flag s are set in the firmware area of the eeprom . th e following abbreviations are used in table 3 . 2 and table 3 . 3 column headings: ? st: start bit ? cb: control bit ? pb: parity bit ? eb: end bit important note regarding full compliance with the as- interface complete specification : in order to achieve full compliance with the as - interface complete specification , the lock_ee_prg flag must be set by the manufacturer of as- i slave modules during the final manufacturing and configuration process and before an as- i slave device is delivered to field application users.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 18 january 28, 2016 table 3 . 2 sap5 master calls and related slave responses note: in extended address mode, the "select bit" defines whether the a - slave or b - slave is being addressed. depending on the type of master call, the i3 bit carries the select bit information (sel) or the inverted select bit information ( sel ? ? ? ? ) in extended address mode. the extended address mode cannot be activated if the eeprom flag lock_ee_prg is at the logic low level. refer to section 4.3 for programming the lock_ee_prg flag. master request slave response instruction name st cb a4 a3 a2 a1 a0 i4 i3 i2 i1 i0 pb eb sb i3 i2 i1 i0 pb eb data _ exchange dexg 0 0 a4 a3 a2 a1 a0 0 d3 sel ? ? ? ? d2 d1 d0 pb 1 0 d3 d2 d1 d0 pb 1 write _ parameter wpar 0 0 a4 a3 a2 a1 a0 1 p3 sel ? ? ? ? p2 p1 p0 pb 1 0 p3 p2 p1 p0 pb 1 address _ assignment adra 0 0 0 0 0 0 0 a4 a3 a2 a1 a0 pb 1 0 0 1 1 0 0 1 write _ exten d e d_id - code_1 wid1 0 1 0 0 0 0 0 0 id3 id2 id1 id0 pb 1 0 0 0 0 0 0 1 delete_ address dela 0 1 a4 a3 a2 a1 a0 0 0 sel 0 0 0 pb 1 0 0 0 0 0 0 1 reset_ slave res 0 1 a4 a3 a2 a1 a0 1 1 sel ? ? ? ? 1 0 0 pb 1 0 0 1 1 0 0 1 read _ i / o - configuration rdio 0 1 a4 a3 a2 a1 a0 1 0 sel 0 0 0 pb 1 0 io3 io2 io1 io0 pb 1 read_id - code rdid 0 1 a4 a3 a2 a1 a0 1 0 sel 0 0 1 pb 1 0 id3 id2 id1 id0 pb 1 read_ extended_ id - code_1 rid1 0 1 a4 a3 a2 a1 a0 1 0 sel 0 1 0 pb 1 0 id3 id2 id1 id0 pb 1 read _ extended_ id - code_2 rid2 0 1 a4 a3 a2 a1 a0 1 0 sel 0 1 1 pb 1 0 id3 id2 id1 id0 pb 1 read_ status rdst 0 1 a4 a3 a2 a1 a0 1 1 sel ? ? ? ? 1 1 0 pb 1 0 s3 s2 s1 s0 pb 1 broadcast (reset) br01 0 1 1 1 1 1 1 1 0 1 0 1 1 1 no slave response
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 19 january 28, 2016 table 3 . 3 sap5 additional master calls for slave configuration master request slave response instruction name st cb a4 a3 a2 a1 a0 i4 i3 i2 i1 i0 pb eb sb i3 i2 i1 i0 pb eb se t_id - code (rdio) 0 1 a4 a3 a2 a1 a0 1 1 0 0 0 pb 1 0 0 1 1 0 0 1 se t_io_ config (rdid) 0 1 a4 a3 a2 a1 a0 1 1 0 0 1 pb 1 0 0 1 1 0 0 1 set_ extended_ id - code_ 2 (rid1) 0 1 a4 a3 a2 a1 a0 1 1 0 1 0 pb 1 0 0 1 1 0 0 1 se t_control_ code (rid2) 0 1 a4 a3 a2 a1 a0 1 1 0 1 1 pb 1 0 0 1 1 0 0 1 se t_control_code_ 2 (res) 0 1 a4 a3 a2 a1 a0 1 0 1 0 0 pb 1 0 0 1 1 0 0 1 en ter_safety_program_ mode prgm 0 1 0 0 0 0 0 1 1 1 0 1 1 1 no slave response
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 20 january 28, 2016 4 eeprom 4.1. overview the sap5 features an on- chip eeprom with typical write and read times according to table 4 . 1 . table 4 . 1 eeprom read and write times parameter symbol min max unit initialization read out time 1) t read_init 50.0 s write time after adra master request 2) t wrt_adra1 38.0 ms write time after adra master request 3) t wrt_adra2 12.5 ms write time after wid1 master request (user access) 2) t wrt_wid1u 38.0 ms write time after wid1 master request (manufacturer access) 3) t wrt_wid1m 25.0 ms single cell write time 4) t wrt_prgm 12.5 ms 1) time includes read out of the configuration block. if r unning in safety mode, the user/firmware area and the safety area will be read out in parallel. 2) the lock_ee_prg flag is set . 3) the lock_ee_prg flag is not yet set . 4) applies to the programming of data in both firmware area and safety area . for security reasons , the memory area is structured in three independent data blocks and a single configuration block containing the security_flag . the data blocks are named user area, firmware area , and safety area , which are defined in ta ble 4 . 2 and table 4 . 4 . the firmware area contains all manufactu ring - related configura tion data; e.g . , selection of optional features, id codes, etc. it can be protected against undesired data modification by setting the lock_ee_prg flag to ?1?. the user area contains only such data that is relevant for changes at the final application (i.e . , field installation of slave module). because the environment where modifications of the user data might become necessary can sometimes be harsh and unpredictable, additional security has been added to the programming of the user area , ensuring a write a ccess cannot result in an undetected corruption of eeprom data. the safety area contains the cryptographic code table for the safety mode. the eeprom cells in the user area, firmware area , and safety area have a word width of 6 bit s . the sixth bit is not shown in table 4 . 2 and table 4 . 4 . the sixth bit of each cell represents the odd parity of the respective data word, providing an additional data security mechanism. the programming of the parity bit is performed automatically during the eeprom write process and cannot be influence d by the user. each eeprom read process ? particularly during initialization of the sap5 ? involves an evaluation of the parity bits. if an incorrect parity bit is found in the user area , the entire user area data is treated as corrupted. the sap5 returns to slave address ?0? and the id_code as well as the io_code are set to f hex . if a false parity bit has been found in one or more cells of the firmware area or the safety area, the status register bit s1 will be set (= ? 1?), signaling the same stat e as if the input pfault had been set ( see section 5.16 ).
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 21 january 28, 2016 4.2. user area programming user area data can be written by an adra or wid1 master request ( see table 3 . 2 ). any such write access is accompanied by two write steps to the security_flag , one before and one after the actual modification of user data. 1. the following procedure is executed when writin g to the user area of the eeprom : 2. the security_flag is programmed to ?1?. 3. the content of the security_flag is read back, verifying it was programmed to ?1?. 4. the user data is modified. 5. a read back of the written data is performed. 6. if the read back has pro ven the successful programming of the user data, the security_flag is programmed back to ?0?. 7. the content of the security_flag is read back, verifying it was programmed to ?0?. successful execution of the eeprom write procedure can be observed in the statu s register contents (refer to table 5 . 21) . if bit s0 is set (logic high) , the write process is not finished yet and the programming data is still volatil e. if bit s3 ( which is the security_flag ) is set, the write procedure did not successfully complete either because the write cycle was interrupted or due to an internal error. in order to program the data correctly , the write request should be repeated. th e status register can be read using the as- i m aster call read_status ( rdst ). in addition to a read out of the data areas, the security_flag of the eeprom is also read and evaluated during sap5 initialization. if the value of the security_flag equals ?1? (e . g . , due to an undesired interruption of a user area write access), the entire user area data is treated as corrupted (see section 5.16 ) . the sap5 ret urns to slave address ?0? and the id_code as well as the io_code are set to f hex . as a result , the programming of the user area data can be repeated. table 4 . 2 sap5 eeprom ? user and firmware area content internal eeprom address bit position eeprom cell content s description user area 0 4 to 0 a [ 4 : 0 ] slave address 1 2 to 0 id1_bit [ 2 : 0 ] id_code_extension_1 (user - configurable) 3 id1_bit3 id_code_extension_1 , a/b slave selection in extended address mode 4 not implemented 2 3 to 0 id1_bit [ 3 : 0 ] id_code_extension_1 (manufacturer - configurable) 4 not implemented 3 4 to 0 not implemented
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 22 january 28, 2016 internal eeprom address bit position eeprom cell content s description firmware area 4 4 synchronous_data_io synchronized data i/o m ode 3 to 0 id_bit [ 3 : 0 ] id_code 5 4 inhibit_write_id1 id_code_extension_1 is manufacturer configurable ; refer to section 5.20 3 to 0 id2_bit [ 3 : 0 ] id_code_extension_2 6 4 p1_delay_activation if flag is set, the logic value at the parameter pin p1 determines whether the delay_mode function is active or inactive ; refer to table 5 . 11 3 to 0 io_bit [ 3 : 0 ] io_code 7 4 lock_ee_prg programming of the eeprom firmware region is possible as long as this flag is not set (logic low). 3 delay_mode a ctivates the delay_mode function, refer to table 5 . 11 2 invert_data_in all data port inputs are inverted. 1 inhibit_br01 if flag is set, the master call br01 is not executed. 0 inhibit_watchdog if flag is set, the watchdog is not activated. 8 4 p2_sync_activation the synchronized data i/o m ode can be activated by p arameter bit p2 as described in table 5 . 12. 3 ext_addr_4i/4o_mode 4 inpu t/ 4 output mode in extended address mode 2 parallel_out_4i/4o e nables the parallel data output option in extended address 4i/4o mode 1 master_mode master / repeater mode flag 0 p0_watchdog_activation the watchdog can be enabled / disabled by the logic value at the parameter pin p0 9 4 to 0 analog circuitry trim information 10 11
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 23 january 28, 2016 4.3. firmware area programming in order to p rogram one of the 5 - bit cells in addresses 4 to 8 in the firmware area , a special master call according to table 4 . 3 must be applied, followed immediately by a dexg or wpar call. writ e access to the firmware area is possible as long as the lock_ee_prg flag is not set. the write procedure is started after receipt of the dexg / wpar call. completion of the write procedure can be observed at the status register s0 as described in section 4.2 . the analog circui try trim information (address 9 to 11) can be written by special test mode operation only. it is not possible to read out the eeprom data directly. however, as- i - related configuration data such as id_code can be read by the respective read_id_code ( rdid ) master request. table 4 . 3 sap5 eeprom ? user and firmware area programming note: see table notes at the end of the table. internal eeprom address eeprom cell content programming master calls user area 0 a[ 4 : 0 ] adra master call 1 id1_bit [ 3 :0] wid1 master call 2 id1_bit [3: 0 ] 3 not implemented firmware area 4 synchronous_data_io i4 set id code ( rdio ) master call 1) + dexg/wpar master call 2) id_bit [3: 0 ] i3 to i0 5 inhibit_write_id1 i4 set id code 2 (rid1) master call 1) + dexg/wpar master call 2) id2_bit [3: 0 ] i3 to i0 6 p1_delay_activation i4 set io config (rdid) master call 1) + dexg/wpar master call 2) io_bit [3: 0 ] i3 to i0 7 lock_ee_prg i4 set control code (rid2 ) master call 1) + dexg/wpar master call 2) delay_mode i3 invert_data_in i2 inhibit_br01 i1 inhibit_watchdog i0
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 24 january 28, 2016 internal eeprom address eeprom cell content programming master calls 8 p2_sync_activation i4 set control code 2 (res) master call 1 + dexg/wpar master call 2 ext_addr_4i/4o_mode i3 parallel_out_4i/4o i2 master_mode i1 p0_watchdog_activation i0 9 analog circuitry trim information accessible by idt only 10 11 1) according to table 3 . 3 . 2) according to table 3 . 2 with information bits corresponding to the left column; dexg if i4 = ? 0?, wpar if i4 = ?1?. note: in contrast to regular wpar / dexg calls, the slave always returns the received data bits i3 to i0 for these master calls. 4.4. safety area programming (sap5s only) the safety area contains the cryptographic code table , which consists of 8 data words and one swap - flag each (refer to section 5.18 for an explanation of the sap5 safety mode ). similar to the firmware are a , it can be protected against undesired data modification by setting the safety_program_mode_disable flag ; see address 31 in table 4 . 4 . note : once the safety_program_mode_disable flag is set, the safety area of the eeprom is permanently locked ; i.e. , write access to the safety area as described in table 4 . 4 is possible only as long as the safety_program_mode_disable flag is not set . table 4 . 4 sap5 eeprom ? safety area content logical eeprom address bit position eeprom cell content description 1 4 s_flag_ 0 swap - flag 0 3 to 0 di_s0 [ 3 : 0 ] data input word 0 from safety code table 2 4 s_flag _ 1 swap - flag 1 3 to 0 di_s1 [3:0] data input word 1 from safety code table 3 4 s_flag _ 2 swap - flag 2 3 to 0 di_s2 [3:0] data input word 2 from safety code table 4 4 s_flag _ 3 swap - flag 3 3 to 0 di_s3 [3:0] data input word 3 from safety code table 5 4 s_flag _ 4 swap - flag 4 3 to 0 di_s4 [3:0] data input word 4 from safety code table
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 25 january 28, 2016 logical eeprom address bit position eeprom cell content description 6 4 s_flag _ 5 swap - flag 5 3 to 0 di_s5 [3:0] data input word 5 from safety code table 7 4 s_flag _ 6 swap - flag 6 3 to 0 di_s6 [3:0] data input word 6 from safety code table 8 4 s_flag _ 7 swap - flag 7 3 to 0 di_s7 [3:0] data input word 7 from safety code table 31 1 safety_mode_enable if set, safety mode is enabled 0 safety_program_mode_disable if set, safety area is protected against over wr i t ing similar to the firmware area programming, safety area programming is intended to be used only during production set - up of a slave component at the manufacturer?s site. write a ccess to the safety area of the eeprom is possible in the safety program mode . it can be entered only if the safety_program_mode_disab le flag is not yet set to ?1? and if the slave address has been set to 0 hex . if the slave address equals 0 hex , the reception of the enter_program_mode_safety ( prgm ) call sets the sap5 device into the safety program mode . it should be noted that no response is generated to the enter_program_mode_safety call (refer to the as- interface complete specification ). i n the safety program mode , the write_parameter ( wpar ) and data_exchange ( dexg ) calls are used to transfer data words to the eeprom similar to the firmware area write procedure described in section 4.3 . however, the address bits a [ 4 : 0 ] of the master telegrams are used to address one of the memor y locations of the eeprom (refer to table 4 . 4 ). the information bits i [ 4 : 0 ] (normally used for output data) carry the data to be stored. any wpar or dex g call initializes an autonomous write process within the sap5 . the status of the write process can be monitored by evaluating the status register of the sap5 as described in section 4.1 . since the sap5 is still in safety program mode , the address within the read_status master call has the ?don?t care ? status . in order to execute as many write procedures as desired, do not lea ve the safety program mode until finished . note: t he sap5 will leave the safety program mode and start it s initialization procedure if it receives a reset_slave ( res ) master call to any desired slave address. any attempt to access one of the un available e eprom address locations (0, 9 to 30) of the safety area via a write_parameter ( wpar ) or data_exchange ( dexg ) command will be ignored. there is no direct read access to the safety area data in safety program mode . a fter programming the safety area, a n eepro m verification procedure should be performed; i . e . , by performing one complete as - i safety cycle (8 dexg calls at intervals of at least 250 s) in safety mode operation.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 26 january 28, 2016 5 detailed functional description 5.1. power supply the power supply block provides a sensor supply, which is inductively decoupled from the as- i bus voltage, at the uout pin . the decoupling is realized by a n electronic indu ctor circuit, which basically consists of a current source and a controlling low pas s filter . the time constant of the low pass , which affects the resulting input impedance at the l tgp pin , can be adjusted by an external capacitor at the cdc pin . a second function of the power supply block is to generate a regulated 5v supply for operatio n of the internal logic and some of the analog circuitry. the voltage is provided at the u5r pin and can be used to supply external circuitry as well if the current requirements stay within in the specified limits ( see table 2 . 2 ). because the 5v supply is generated from the decoupled sensor supply at uout, the current drawn at u5r must be subtracted from the total available load current at uout. the power supply dissipates most of the power (see table 5 . 1 ) : p tot = v drop ? (i uout + i 5v ) + (v uout - 5v) ? i 5v in total, the power dissipation must not exceed the specified values in section 2.1 . to cope with fast internal and external load changes (spikes) , external capacitors at uout and u5 r are required. the ltgn pin defines the ground reference voltage for both uout and u5r. 5.1.1. voltage output pins uout and u5r table 5 . 1 properties of v oltage o utput p ins uout and u5r parameter symbol conditions min max unit positive supply voltage for sap5 operation 1) v ltgp 16 34 v voltage drop from ltgp pin to uout pin v drop v ltgp > 22v 5.2 7.8 v uout output supply voltage v uout i uout = i uoutmax v ltgp - v dropmax v ltgp - v dropmin v uout output voltage pulse deviation 2) v uoutp c uout = 10f 1.5 v uout output voltage pulse deviation width 2) t uoutp c uout = 10f 2 ms 5v supply voltage v u5r 4.75 5.25 v uout output supply current i uout i u5r = 0 v ltgp >24v 0 55 ma u5r output supply current i u5r 0 4 ma total output current i uout + i 5v i o 60 ma blocking capacitance at uout c uout 10 470 f blocking capacitance at u5r c u 5 r 1 00 n f 1) parameter is also given in table 2 . 2 . 2) c uout = 10f ; output current switches from 0 to i uoutmax and vice versa .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 27 january 28, 2016 5.1.2. input impedance ( as - interface b us l oad) table 5 . 2 as - interface bus load properties parameter symbol conditions min max unit equivalent resistor of the sap5 1), 2) r in1 13.5 k ? equivalent inductor of the sap5 1), 2) l in1 13.5 mh equivalent capacitor of the sap5 1), 2) c in1 30 pf equivalent resistor of the sap5 1), 2) r in2 13.5 k ? equivalent inductor of the sap5 1), 2) l in2 12 13.5 mh equivalent capacitor of the sap5 1), 2) c in2 15 + (l - 12mh) ? 10pf/mh pf parasitic capacitance of the external over - voltage protection diode (zener diode) 1) c zener 20 pf 1) the equivalent circuit of a slave, which is calculated from the impedance of the sap5 and the parallel external over - voltage protection diode (zener diode), must satisfy the requirements of the as - interface complete specification for extended address mode slaves. 2) after the maximum parasitic capacitance of the external over - voltage protection diode (20pf) has been subtracted, the specifications group including r in1 , l in1 and c in1 or the specifications group including r in2 , l in2 and c in2 must be met for compliance with the as- interface complete specification v3.0 . table 5 . 3 cdc p in p arameters parameter symbol conditions min typical max unit input voltage range v cdc_in - 0.3 v u5r v external decoupling capacitor c cdc 100 nf note: a decoupling capacitor defines the internal low - pass filter time constant; lower values decrease the impedance but improve the turn - on time. higher values do not improve the impedance but do increase the turn - on time. the turn - on time also depends on the load capacitor at uout. after connecting the slave to the power , the capacitor is charged with the maximum current i uout . the impedance will increase when the voltage allows the analog circuitry to fully o perate.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 28 january 28, 2016 5.2. thermal protection the sap5 continuously monitors its silicon die temperature. if the temperature rises above approximately 140c for more than 2 seconds , the sap5 will cut off the uout output from the internal voltage reference. thus the current consumption of the sap5 will drop down to its operating current (refer to table 2 . 2 ). in order to prevent an undesired drawing of transmit ter current , the transmitter is also disabled if t he over - temperature cut off condition occurs . after an over - temperature cut - off, if the die temperature has cooled down by 10 to 20c, t he output voltage at uout will be restored and the sap5 performs an initialization with an additional time delay of 1s. table 5 . 4 cut - off temperature parameter symbol conditions min max unit chip temperature for over - temperature shut down t cutoff 125 160 c 5.3. dc characteristics ? digital inputs the following pins contain digital high - voltage input stages: input - only pin: pfault i/o pins: p1, p3, d1, d3, dstbn, pstbn, led1 (pstbn and led1 are inputs for test purposes only) 3 - level i/o pins: p0, p2, d0, d2 (see table note s 1) and 2) in table 5 . 5 ) table 5 . 5 dc characteristics of digital high voltage input pins parameter symbol conditions min max unit voltage range for input ? offset_low? level 1) , 2) v ofl 0 1.0 v voltage range for input ? offset_high? level 1) , 2) v ofh 1.6 v uout v voltage range for input ? low? level 2) v il2 0 2.5 v voltage range for input ? high? level v ih 3.5 v uout v current range for input ? low? level 3) i il v in = 1v -12 -3 a current range for input ? high? level i ih v 0 v u5r -10 10 a capacitance at pin dstbn 4) c dl 10 pf 1) the p0, p2, d0, d2 pins are used as 3 - level inputs, i.e. inputs with offset detection, in safety mode only; otherwise configuration depends on the slave profile. refer to table 5 . 15 . 2) the 3 - level input pads contain independent comparators for the detectio n of regular input data level and offset. refer to figure 5 . 8 for constraints to the externally applied voltages in safety mode . 3) the pull - up current is driven by a current source connected to u5r. it stays almost constant for input voltages ranging from 0 to 3.8v. 4) the internal pull - up current is sufficient to avoid accidental triggering of an sap5 reset if the dstbn pin remains unconnected. for external loads at dstbn , a sufficient pull - up resistor is required to ensure v ih 3.5v in less than 90ms after the beginning of a dstbn = l ow pulse.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 29 january 28, 2016 5.4. dc characteristics ? digital outputs the following pins contain digital high - voltage, open - drain output stages: output - only pin: led2 i/o pins: d [3: 0 ], p [3: 0 ] , dstbn, pstbn, led1 (pstbn and led1 are inputs for test purposes only) table 5 . 6 dc characteristics of digital high voltage output pins para meter symbol conditions min max. unit voltage range for output ? low? level v ol1 i ol1 = 10ma 0 1 v voltage range for output ? low? level v ol2 i ol2 = 2ma 0 0.4 v output leakage current i oh v 0h v u5r -10 10 a a slew rate limitation is applied to each digital high voltage output driver that limits the rise and fall times for both high/low and low/high transitions to 40 to 50 ns. note: the rise time for a low/high transition is primarily influenced by the external pull - up resistor. 5.5. as - i receiver the receiver detects (telegram) signals at the as - i line, converts them to digital pulses , and forwards them to the uart for further processing. the receiver is internally connected between the ltgp and ltgn pins. functional, the receiver removes the dc value of the input signal, band - pass filters the ac signal , and extracts the digital output signals from the sin 2 - shaped input pulses via a set of comparators. the amplitude of the first pulse determines the threshold level for all following pulses. this a mplitude is digitally filtered to guarantee stable conditions and to suppress burst spikes. this approach combines a fast adaptation to changing signal amplitudes with a high detection safety. the comparators are reset after every detection of a telegram p ause at the as- i line. when the receiver is turned on, the transmitter is turned off to reduce the power consumption. table 5 . 7 receiver parameters parameter symbol conditions min max unit ac signal peak - peak amplitude (between ltgp and ltg n) v sig 3 8 v pp receiver comparator threshold level (refer to figure 5 . 1 ) v lsigon rel ative to first pulse amplitude 45 55 %
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 30 january 28, 2016 5.6. as - i transmitter figure 5 . 1 basic receiver comparator threshold set - up principle s first negative pulse of the as - i telegram v lsigon v lsigon = (0.45 to 0.55) ? v sig / 2 dc level v sig / 2 the ic determines the amplitude of the first negative pulse of the as - i telegram. this amplitude is asserted to be v sig / 2. the transmitter draws a modulated current between ltgp and ltgn to generate the communication signals. the shape of the current corresponds to the integral of a sin 2 - function. the transmitter com prises a current dac and a high - cu rrent driver. the driver requires a small bias current to flow. the bias current is ramped up slowly for a specific time before the transmission starts so that any false voltage pulses on the as - i line are avoided. when the transmitter is turned on, the r eceiver is turned off to reduce the power consumption. the sap5 includes a clock watchdog that becomes activated once the clock sig nal is stopped for approximately 100s to 150s so that the transmitter is prevented from being permanently switched on in ca se the clock signal is missing. table 5 . 8 transmitter current amplitude parameter symbol min max unit modulated transmitter peak current swing (between ltgp and ltg n) i sig 55 68 ma p 5.7. parameter port and pstbn the parameter port is always configured for continuous bi - directional operation. however, if io_code = 7 hex (see table 5 . 14 ), the parameter ports will return to high impedance state immediately after a wpar request because they act as data input ports or safety data ports for a subsequent dexg master call. every pi n contains an nmos open - drain output driver plus a high - voltage , high - impedance digital input stage. received parameter output data is stored in the parameter output register and sub sequently forwarded to the open- drain output drivers. a specific time (t pi- latch ) after new output data has arrived at the port, the corresponding inputs are sampled. due to the open - drain of the output driver, the input value results from a wired and combination of the parameter output value and such signals driven to the port by external sources.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 31 january 28, 2016 the availability of new parameter output data is signaled by the parameter strobe (pstbn) signal as shown in figure 5 . 2 . in addit ion to the basic i/o function, the first parameter output event after an sap5 reset has an additional effect . it enables the data exchange functionality. any sap5 reset sets the parameter output register to f hex and forces the parameter output drivers to the high impedance state. simultaneously, a parameter strobe is generated with the same t setup timing and t pstbn pulse width as would be used to drive new output data. table 5 . 9 timing for parameter port s par ameter symbol conditions min max unit output data is valid after pstbn high - low edge t stb 0.0 1.5 s pulse width of parameter strobe (pstbn) 1) t pstbn 6.0 6.8 s acceptance of input data 2) t pi - latch 10.5 12.5 s parameter port is at high impedance state after pstbn high - low edge 3) t p - off 56.0 64.5 s 1) the timing of the resulting voltage signal also depends on the external pull up resistor. 2) the parameter input data must be stable within the period defined by min. and max. values of t pi - latch . 3) concerns the io configuration ?7? only (see table 5 . 14) . figure 5 . 2 timing diagram for parameter port p [3: 0 ] , pstbn pstbn parameter port output data parameter input value ( pix ) = parameter output value ( pox ) ( wired and with external signal source value ) keep stable min max p [ 3 : 0 ] t pi - latch t pstbn t p - off t stb
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 32 january 28, 2016 5.8. data port and dstbn 5.8.1. timing of data i/o and dstbn every data pin (d0 to d3) contains an nmos open - drain output driver as well as a high - voltage, high - impedance input stage. received output data is stored in the data output register and subsequently forwarded to the data pins. a specific time (t di- latch ) after new output data has been written to the port the input data is sampled. the availability of new output data is signaled by the data strobe (dstbn) signal as shown in figure 5 . 3 . the dstbn pin has an additional reset input function, which is described further in section 5.13 . any sap5 reset sets th e data output register to f hex and forces the data output drivers to the high - impedance state. simultaneously, a data strobe is generated with the same t setup timing and t dstbn pulse width as would be used to drive new output data . table 5 . 10 timing for data port outputs parameter symbol conditions min max unit output data is valid after dstbn high/low edge t stb 0.0 1.5 s output driver is at high impedance state after dstbn low/high 1) t hold 0.2 1.0 s pulse width of data strobe (dstbn) 2) t dstbn 6.0 6.8 s acceptance of input data 3) t di - latch 10.5 12.5 s 1) parameter is only valid if the respective data port is configured as an i/o pin . 2) the timing of the resulting voltage signal al so depends on the external pull - up resistor. 3) the input data must be stable w ithin the period defined by minimum and maximum values of t di - latch . 5.8.2. input data pre - processing figure 5 . 3 timing diagram for data port d [3: 0 ] and dstbn dstbn data port output data d [ 3 : 0 ] t di - latch t dstbn t stb keep stable data port input data t hold min max
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 33 january 28, 2016 in addition to the standard input function , the data port has data pre - processing features that can be activated by setting corresponding flags in the firmware area of the eeprom . ? input inverting : the input values of all four data input channels are inverted if the invert_data_in flag is ?1? ? input delay : if the delay mode is activated, a new input value is returned to the master if equal input data was sampled for two consecutive data_exchange cycl es. as long as the condition is not true, previous valid data is returned. to suppress undesired input data validation in the event of immediately repeated data_exchange calls (i. e. , as - i m asters immediately repeat a data_exchange request if no valid slave response was received on the first request) , input data sampling is blocked for 256s ( - 6.25%) after every sampling event. the filter output of each data port is preset to ?0? after reset or as long as the data_exchange_disable flag is s et. figure 5 . 4 principle s of delay mode input filtering ? example for slave with address 1 hex > 256s (-6.25 %) dexg addr 1 dexchg addr 1 dexg addr 1 slave slave slave input signal f ilter output s ampling point < 256 s ( - 6 . 25 %) this sampling event is blocked to avoid immediate input data validation activation of delay mode depends on the eeprom flags delay_mode and p1_delay_activation and the value of the parameter port p1 output register as shown in table 5 . 11 . delay mode cannot be activated when safety mode is en abled. note: the input signal at parameter port p1 does not affect activation of input delay mode . only the master can change the activation status by sending a corresponding write_parameter ( wpar ) request. table 5 . 11 activation of delay mode delay_mode p1_delay_activation parameter p1 output register delay mode 0 x x off 1 0 x on 1 1 1 off 1 1 0 on
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 34 january 28, 2016 5.8.3. synchronous data i/o mode since the slaves in an as - i network are called successively by the master, the data input and output operati ons of different slaves are not normally synchronized. if there is, however, an application that requires accurate synchronized data i/o timing, the respective slaves can be o perated in the synchronous data i/o mode . with respect to communication with the master, slaves running in the synchronous data i/o mode behave like regular slaves. however, the input data sampling as well as the output data driving is determined by the po lling cycle of the respective as- i network as described below. activation of the sap5 synchronous data i/o mode is related to the eeprom flags synchronous_data_io and p2_sync_activation (refer to table 4 . 2 ) and the value of the parameter port p2 output register as follows: note: the input signal at parameter port p2 does not affect activation of synchronous data i/o mode . only the master can change the activation status by sending a corresponding write_parameter ( wpar ) request. table 5 . 12 activation of the synchronous data i/o mode synchronous_data_io p2_sync_activation param eter p2 ou t put register synchronous data i/o mode 0 x x off 1 0 x on 1 1 1 off 1 1 0 on note: the synchronous data i/o mode is not available if the safety mode is enabled. if synchronous data i/o mode is activated , input data sampling as well as the output data driving events are moved to different times synchronized to the polling cycle of the as - i network. nevertheless, the communication principles between master and slave remain unchanged compared to regular operation. the f ollowing rules apply: ? da ta i/o is triggered by the dexg call to the slave with the lowest slave address in the network. based on the fact that a master is calling slaves successively with rising slave addresses, the sap5 consi ders the trigger condition true if the slave address o f a received dexg call is less than the slave address of the previous correctly received dexg call. ? data i/o is only triggered if the slave has correctly received data during the last cycle. if the slave did not receive data (i.e. , due to a communication e rror) , the data outputs are not changed and no data strobe is generated ( the ? arm+fire ? principle). the inputs however, are always sampled at the trigger event. ? if the slave with the lowest address in the network is operated in the synchronous data i/o mod e , it postpones the output event for the received data for a full as - i cycle. this is to keep all output data of a particular cycle image together. note: to make this feature useful, the master must generate a data output cycle image once before the start of every as- i cycle. the image is derived from the input data of the previous cycle(s) and other control events. once an as - i cycle has started, the image must not change . if a and b slaves are installed in parallel at one address, the master must address all a - slaves in one cycle and all b - slaves in the other cycle.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 35 january 28, 2016 ? the input data, sampled at the slave with the lowest slave address in the network, is sent back to the master without any delay. thus, the input data cycle image is fully captured at the end of an as- i cycle, just as in networks without any synchronous data i/o mode slaves. in other words, the input data sampling point has simply moved to the beginning of the as- i cycle for all synchronous data i/o mode slaves. ? if the synchronous data io mode is enabled through eeprom setting ( synchronous_data_io = ?1?, p2_sync_activation = ?0?), the first dexg call that is received by a particular slave after the activation of the data port ( data_exchange_disable flag was cleared by a wpar call) is processed as in standard operation. this is to capture valid input data for the first slave response and to activate the outputs as quickly as possible. ? the data i/o operation is repeated together with the i/o cycle of the other synchronous data i/o mode slaves in the network at the common trigger event. as a result , the particular slave is now in the synchronous data i/o mode . ? if the p2_sync_activation flag is set to ?1 , ? the synchronous data io mode can be activated or deactivated during normal operation by sendin g write_parameter calls containing the appropriate value in p2 (see table 5 . 12 ). ? if the p2 output register changes from ?1? to ?0 , ? the synchronous data io mode is immediately enabled. actual synchronous data i/o operation is reached after reception of the next dexg call addressing the slave and the occurrence of the common trigger event. as in standard operation (synchronous data io mode is activated by the eeprom setting) , the first dexg call still processes a data io operation immediately. this is to capture valid input data for the slave response and to activate the outputs as quickly as possible. ? the data i/o operation is repeat ed together with the i/o cycle of the other synchronous data i/o mode slaves in the network at the common trigger event. as a result, the particular slave is now in the synchronous data i/o mode. ? if the p2 output register changes from ?0? to ?1 , ? the sync hronous data io mode is deactivated and disabled immediately. if a synchronous data i/o event was already scheduled but not yet processed (armed but no t fired) before the synchronous data i/o mode has bec o me deactivated, the associated data output value is lost. ? if p2 changes back to ?0,? r eactivation of the synchronous data i/o mode occurs in same manner as described above . ? to avoid a general suppression of data i/o in the special case that a slave in synchronous data i/o mode receives dexg calls only to its own address (i.e. , employment of a handheld programming device), the synchronous data i/o mode becomes deactivated if the sap5 receives three consecutive dexg calls to its own slave address. the sap5 resumes to synchronous data i/o mode operation after it has observed a dexg call to a slave address that is different from its own. the reactivation of the synchronous data i/o mode is handled in the same manner for the first dexg call after activation of the data port or after activation of the synchronous data i/o mode by p2 changing to ?0? (see description above). if any of the data ports d0 to d3 is configured as a pure output ( designated as ? out ? in table 5 . 14 ), the sap5 returns the output data that was received from the master immediately in its slave response. since there is no input function available at such port s , the return value is independent from a possible synchronous data i/o m ode operation .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 36 january 28, 2016 when r unning in synchronous data i/o mode , the sap5 also generates the data strobe (dstbn) signal ; whereas the timing of input sampling and output buffering corresponds exactly to the standard operation (refer to figure 5 . 3 and table 5 . 10). 5.8.4. support of 4i/4o signa ling in extended address mode in extended address mode , the information bit i3 of the as - i master telegram i s used to distinguish between a and b slaves that operate in parallel at the same as- i slave address. for more detailed information , refer to the as- i nterface complete specification v3.0 . in addition to the benefit of an increased address range, the cycle time per slave is increased in extended address mode from 5ms to 10 ms and the useable output data is reduced from 4 to 3 bits. because of the reduc ed data bits , extended address mode slaves can usually control a maximum of only 3 data outputs. the input data transmission is not a ffected since the slave response still carries 4 data information bits in extended address mode. additionally, the sap5 sup po rts applications that require 4- bit wide outpu t data in extended address mode if the application can tolerate further increased cycle times ( e . g . , push buttons and pilot lights). such applications must be directly characterized by a new slave profile 7.a.x.7 , which is defined in the as - interface complete specifi - cation (see section 9 ). if the sap5 is operated in extended address mode and the ext_ addr_4i/4o_mode flag is set (= ? 1?) in the eeprom (refer to table 4 . 2 ) , it treats information bit i2 as the selector for two 2 - bit wide data output bank s: ? bank_1 = d0/d1 ? bank_2 = d2/d3. a master must consecutively transmit data to bank_1 and bank_2 , toggling the information bit i2 in the respective master calls. however, the sap5 triggers a data output event (modification of the data output ports and generation of data strobe) as follows (see table 5 . 13) : ? if the parallel_out_4i/4o flag is set (= ? 1?) in the eeprom (refer to table 4 . 2 ) , the sap5 triggers a data output event only if information bit i2 is equal to ?0 , ? in which case, new output data is issued at the data port synchronously for both ban ks at the same time. ? if the parallel_out_4i/4o flag is not set (= ? 0?) , the sap5 triggers a data output event at every cycle. however, depending on the information bit i2 , only one bank of the data port gets refreshed.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 37 january 28, 2016 table 5 . 13 meaning of master call bit s i [3: 0 ] with ext_addr_4i/4o_mode = ?1? master call bit operation / meaning parallel_out_4i/4o = ?0? parallel_out_4i/4o = ?1? i2 = ?0? i2 = ?1? i2 = ?0? i2 = ?1? i0 d2 = i0 d3 = i1 d1 = unchanged d0 = unchanged d2 = unchanged d3 = unchanged d1 = i1 d0 = i0 d2 = i0 d3 = i1 d1 = do1_tmp 2) d0 = do0_tmp 2) d2 = unchanged 1) d3 = unchanged 1) d1 = unchanged 1) d0 = unchanged 1) do1_tmp = i1 do0_tmp = i0 i1 i2 i2 = sel ? ? ? ? - bit for transmission to bank_1 (d0/d1) / bank_2 (d2/d3) i3 i3 = sel ? ? ? ? - bit for a - slave/b - slave addressing (see table 3 . 2 ) 1) if i2 = ?1? then i0/i1 are directed to temporary data output registers do0_tmp / do1_tmp . 2) if i2 = ?0? then i0/i1 are directed to the data output registers d2/d3 and do0_tmp / do1_tmp are direct ed to data output registers d0/d1. in order to ensure that both bank_1 and bank_2 data are refreshed continuously, the sap5 supervises the alternation of the i2 sel - bit by use of the 4i/4o watchdog. the 4i/4o watchdog gets activated as soon as x the communication watchdog is activated (refer to section 5.17 and table 5 . 22 ). x the sap5 is operated in extended address mode and the ext_addr_4i/4o_mode flag is set (= ? 1?) in the eeprom . x slave address is not equal to zero (0 hex ). x no eeprom write access is active. x the slave is activated, i.e. the data_ex change_disable flag is cleared (?0?) . if there is no alternation of the i2 bit for more than 327ms (+16ms) after the activation of the slave , the 4i/4o watchdog takes the following actions: x it generates data and parameter strobe signals at the dstbn an d pstbn pins with timing according to figure 5 . 2 and figure 5 . 3 . x after dstbn and pstbn strobe generation has finished, the 4i/4o watchdog invokes an unconditioned sap5 r eset. it sets the data_exchange_disable flag and afterwards starts the sap5 initialization procedure, switching all data and parameter out puts inactive. input data is captured and returned to the master at every cycle, independent of the value of information bit i2 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 38 january 28, 2016 5.8.5. special f unction of dstbn in addition to the standard output function , the data strobe pin serves as an external reset input for all operational modes of the sap5 . pulling the dstbn pin low for more than a minimum reset time generates an unconditioned reset of the sap5 , which is immediately followed by an initialization of the s tate m achine ( eeprom read out). f or f urther information on the sap5 reset behavior, especially in regard to the signal timing, see section 5.13 . 5.9. data and parameter port co nfiguration data and parameter p orts are configured by programming the io_code in the eeprom (see table 4 . 2 ) . t he configuration also depends on the safe ty_mode_enable setting (see table 4 . 4 ) . table 5 . 14 lists the different configurations selected by the io_code settings. note : table 5 . 14 refers to slaves that are not running in safety mode ( for safety mode details, see section 5.18 ) the following configurations are possible: ? out : output only ; data are valid up to the next dstbn/pstbn strobe pulse ? in : input only; open - drain output is fixed at the high - impedance state ? i/o : bi - directional port with timing according to figure 5 . 2 and figure 5 . 3 ? inout : if io_code = 7 , the parameter p orts are configured as outputs after wpar master calls and as inputs after dexg master calls, respectively. ? passiv : no input function and open - drain output is fixed at the high - impedance state if any of the d0 to d3 data ports is configured as out, the sap5 slave answer to a dexg master request contains the respective information bit i [3: 0 ] received from the master. however, p arameter p orts p [3: 0 ] are always operated as bi - directional, including a read - back of the actual port level as described in section 5.8 . table 5 . 14 data and parameter port configuration for non - safety - mode operation note: see important table notes at the end of the table. io_code d0 d1 d2 d3 1) p0 p1 p2 p3 1) 0 in in in in out out out out 1 in in in out out out out out 2 in in in i/o out out out out 3 in in out out out out out out 4 in in i/o i/o out out out out 5 in out out out out out out out 6 in i/o i/o i/o out out out out 7 2) out out out out inout inout inout inout 8 out out out out out out out out 9 out out out in out out out out a out out out i/o out out out out
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 39 january 28, 2016 io_code d0 d1 d2 d3 1) p0 p1 p2 p3 1) b out out in in out out out out c out out i/o i/o out out out out d out in in in out out out out e out i/o i/o i/o out out out out f 3) passiv passiv passiv passiv out out out out 1) slaves running in extended_address_mode ( id_code = a hex ) will output the respective select bit (i3) at the p3 pin and also at the d3 pin if it is configured as out or i/o. 2) the special case io_code = 7 hex causes the parameter ports to act as data inputs after dexg master calls. thus a bi - directional data exchange with separate data inputs and outputs is possible. parameter ports are always out puts after wpar master calls. note: io_code = 7 hex is not allowed for the 16- p in version of the sap5 . 3) there is no data exchange possible i f io_code = f hex ; i.e. data outputs are always at the high impedance state, and no slav e answer is generated upon rece ption of dexg master calls. table 5 . 15 data and parameter port configuration in safety mode note: see section 5.18 for an explanation of f - dx. package io_code d0 d1 d2 d3 p0 p1 p2 p3 1) 16 pin 0 to 6 8 to f f - d0* in d0* out f - d2* in d2* out don?t care don?t care don?t care don?t care 16 pin 7 1) don?t care don?t care don?t care don?t care don?t care don?t care don?t care don?t care 20 pin 0 to 6 8 to f f - d0* in d0* out f - d2* in d2* out p0 out p1 out p2 out p3 out 20 pin 7 2) d0 out d1 out d2 out d3 out f - d0* in p0 out d0* out p1 out f - d2* in p2 out d2* out p3 out 1) io_code = 7 hex is not allowed for the 16 - pin version for the sap5. 2) parameter ports are parameter outputs during wpar master calls and after dexg master calls. they are in the high impedance state after wpar master calls and act as input s when a dexg master call is perfo rmed. 5.10. fault indication input pfault the pfault fault indication input pin is provided for sensing a periphery fault - messaging signal. it co ntains a high - voltage, high - impedance input stage that sets the status bit s1 of the as- i slave to ?1? if it detects a low level at the pfault pin. the dc properties of the pin are specified in table 5 . 5 . signal transitions at the pfault pin are indicated in s1 with a slight delay because the signal is first processed by a clock synchronizing circuit .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 40 january 28, 2016 5.11. led o utputs 5.11.1. slave mode the sap5 provides two led pins for enhanced status indication. led1 and led2 both comprise nmos open - drain output driver s. in addition, led2 contains a high - voltage, high - impedance input stage for purposes of the sap5 production test. note: in order to comply with the signaling schemes defined in the as- interface complete specification , a red led must be connected to led2 and a green led must be connected to led1. the f ollowing status indication is supported : table 5 . 16 led s tatus i ndication priority /s tatus led1 / led 2 note s 1. power o ff no power supply available . 2. external r eset dstrbn pin driven low for more than 90ms. 3. periphery f ault a lternating periphery f ault signal generated at pfault input pin as described in section 5.10 . 4. no data exchange (address = 0) slave is waiting for address assignment. data port communication is not possible. 5. no data exchange the sap5 was reset by the c ommunication watchdog or by res or br01 master calls ; t hus the data_exchange_disable flag is still set, prohibiting data port communication. the sap5 is waiting for a write_parameter request. this status is not signaled if the communication watchdog is not activated (see section 5.17 ). 6. normal operation data communication is established . the flashing frequency of any flashing status indication is approximately 2 hz . in the case of a simultaneous occurrence of several states , the status with the highest priority is signaled. gree n red red green red green red gr een red red red red red
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 41 january 28, 2016 5.11.2. master/repeater mode in the master/repeater mode , led1 provides the manchester - ii- coded, re - synchronized equivalent of the tele - gram signal received at the as- i input channel. every as - i telegram received is checked for consistency with the protocol specifications , and timing jit ters are removed if they stay within the specified limits. if a telegram error is detected, the output becomes inactive for a certain time period ; see section 5.19.3 for details . led2 is always logic high (high impedance) in master/repeater . in such applications, the green led must be connected to the uout pin or different supply levels. 5.12. oscillator pins osc1 and osc2 table 5 . 17 oscillator p in p arameters parameter symbol conditions min typ max unit input voltage range v osc_in - 0.3 v u5r v external parasitic capacitor at oscillator pins osc1, osc2 c osc 0 8 pf dedicated load capacity c load 12 pf input ?low? voltage for external clock applied to osc1 v il 0 1.5 v input ?high? voltage for external clock applied to osc1 v ih 3.5 v u5r v the oscillator supports direct connection of 5.33mhz or 16.000mhz crystals with a dedicated load capacity of 12pf and parasitic pin capacities of up to 8pf. the sap5 automatically detects the oscillation frequency of the connected crystal and controls the internal clock generator circuit accordingly. the oscillator u nit also contains a clock watch dog circuit that can generate an unconditioned sap5 reset if there has been no clock oscillation for more than about 20s. this is to prevent the sap5 from unpredi ct able behavior if the clock signal is no longer available. 5.13. sap5 reset any sap5 reset sets the data output and parameter output registers to f hex and forces the corresponding output drivers to the high impedance state. except on pow er - on reset, the data strobe ( dstbn ) and parameter strobe ( pstbn ) signals are simultaneously generated to indicate possibly changed output data to external circuitry. the data_exchange_disable flag is set during an sap5 reset, prohibiting any d ata p ort activity immediatel y after sap5 initialization and as long as the external circuitry was not pre - conditioned by valid parameter output data. c onsequently the as - i master must send a write_parameter call in advance of the first data_exchange request to an initialized slave. the sap5 initialization times are given in table 5 . 18 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 42 january 28, 2016 table 5 . 18 sap5 initialization t imes parameter sy mbol conditions min max unit initialization time after software reset (generated by master calls reset_slave or broadcast_reset ) or external reset via ds tbn 1) t init 2 ms initialization time after power on 2) t init2 c uout 10f 30 ms initialization time after power - on with high capacitive load 1) t init3 c uout = 470f 1000 ms 1) guaranteed by design. 2) power starts when v ltgp = 18v at the latest. 5.13.1. power - on reset in order to force the sap5 i nto a defined state after power - on and to avoid uncontrolled switching of the digital logic if the 5v supply (u5r) falls below a specified minimum level, a power - on reset is executed under the conditions given in table 5 . 19. table 5 . 19 power - on reset (por) threshold voltages parameter symbol conditions min max unit v u5r voltage to trigger internal reset procedure, falling voltage 1) v por1f 1.2 1.7 v v u5r voltage to trigger initialization procedure, rising voltage 1) v por1r 3.5 4.3 v power -o n r eset pulse width t l ow 4 6 s 1) guaranteed by design. figure 5 . 5 power - on behavior (all modes) ltgp u5r reset approx. 15v t low v por 1 r v por 1 f note: the power - on reset circuit has a threshold voltage reference. this reference matches the process tolerance of the logic levels and ther efore is not accurate. all values depend slightly on the rise and fall time of the supply voltage.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 43 january 28, 2016 5.13.2. logic c ontrolled reset the sap5 also becomes reset after reception of reset_slave or broadcast_reset commands, expiration of the (enabled) communication watchdog , or entering a prohibited state machine state (i.e. , due to heavy emi). 5.13.3. external reset the sap5 can be reset externally by pulling the dstbn pin low for more than the minimum reset time. the external reset input function is provided in every operational mode of the sap5: slave mode and master/repeater mode . the signal timings are given in table 5 . 20 . table 5 . 20 timing of external reset parameter symbol conditions min max unit ds tbn low time for no reset initiation t noreset 90 ms reset execution time : dst b n h/l transition to hi - z output drives at do[3:0], p[3:0] t reset 99 ms state machine initialization time after reset (eeprom read out) t init 2 ms figure 5 . 6 timing diagram extern al reset via dstbn dstbn d[3:0] t noreset p[3:0] hi-z data port output data parameter port output data external reset t reset hi-z t init the external reset is generated as ?edge sensitive? to the expiration of the t reset timer. the initialization procedure is starting immediately after the event, independent of the state of dstbn. the external reset state persists if dstbn still remains low after t reset + t init . the corresponding error state display is described in section 5.11 . 5.14. uart the uart performs a syntactical and timing analysis of the telegrams received at the as- i input channel. it converts the pulse - coded as - i input signal into a manchester - ii- coded bit stream and provides the receive register with decoded telegram bits. the uart also realizes the manchester - ii- coding of a slave answer.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 44 january 28, 2016 in master/repeater mode , the output signal of the manchester coder ( as- i pulse to man signal conversion) is resynchronized and forwarded to the led1 pin . any pulse timing jitters of the received as - i signal are removed if they are within the specified maximum limits. if the received as- i telegram does not pass one of the error checks (see detailed description below), the led1 output becomes inactive for a certain time period ; see section 5.19.3 . the comparator stages at the as- i line receiver generate two pulse - coded output signals ( p_pulse , n_pulse ) disjoining the positive and negative telegram pulses for f urther processing. to reduce uart sensitivity to erroneous spike pulses, pulse filters suppress any p_pulse , n_pulse activity of less than 750 ns width. after filtering, the p_pulse and n_pulse signals are checked in accordance with the as - interface complet e specification for the following telegram transmission errors: start_bit_error the initial pulse following a pause must have negative polarity. violation of this rule is detected as a start_bit_error . the first pulse is the reference for bit decoding. the first bit detected must be the value 0. alternating_error two consecutive pulses must have different polarity. violation of this rule is detected as an alternating_error . note: a negative pulse must be followed by a positive pulse and vice versa. timing _error within any master request or slave response, the digital pulses that are generated by the receiver are checked to start in periods of s s s n + ? ? 500 . 1 875 . 0 ) 3 ( after the start of the initial negative pulse, where n = 1 to 26 for a master request and n = 1 to 12 for a slave response. violation of this rule is detected as a timing_error. note: there is a certain pulse timing jitter associated with the receiver output signals (compared to the analog signal waveform) due to sampling and offset effects at the comparator stages. in order to take the jitter effects into account, the timing tolerance specifications differ slightly from the definitions of the as- interface complete specification . no_information_error derived from the manchester - ii- coding rule, either a positive or negative pulse must be detected in periods of s s s n + ? ? 500 . 1 875 . 0 ) 6 ( after the start of the initial negative pulse, where n = 1 to 13 for a master request and n = 1 to 6 for a slave response. violation of this rule is detected as a no_information_error . note: the timing specification relates to the receiver comparator output signals. there is a certain pulse timing jitter in the digital output signals (compared to the analog signal waveform) due to sampling and offset effects at the comparator stages. in order to take the jitter effects into account, the timing tolerance specifications differ slightly from the definitions of the as- interface complete specification . parity_error the sum of all information bits in master requests or slave responses (excluding the start and end bits, including the parity bit) must be even. violation of this rule is detected as a parity_error. end_bit_error the pulse to be detected s s s n + ? ? 500 . 1 875 . 0 ) 6 ( after the start pulse must be of positive polarity, where n = 13 (78 s) for a master request and n = 6 (36 s) for a slave response. violation of this rule is detected as an end_bit_error. note: this stop pulse must finish a master request or slave respo nse. length_error telegram length supervision is processed as follows. if during the first bit time after the end pulse of a master request (equivalent to the 15 th b it time) for synchronized slaves , or during the first three bit times for non- synchronized slaves ( equivalent to the b it times 15 to 17) , or during the first bit time after the end pulse of a slave response (equivalent to the 8 th b it time) , a signal other than a pause is detected, a length_error is detected.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 45 january 28, 2016 if one or more of these errors occurs, the received telegram is treated as invalid. in this case, the uart will not generate a receive strobe signal. it moves to asynchronous state and wait s for a pause at the as - i line input. after a pause has been detected, the uart is ready to receiv e the next telegram. receive strobe signals are generally used to validate the correctness of the received data. a receive strobe starts the internal processing of a master request. if the uart was in asynchronous state before the signal was generated, it transforms to synchronous state afterwards . if the received slave address matches the stored address of the sap5 , the transmitter is turned on by the receive strobe pulse, allowing the output driver to settle smoothly at the operation point (avoiding false pulses at the as - i line). 5.15. main state machine the main state machine controls the overall behavior of the sap5 . depending on the configuration data stored in the eeprom , the state machine activates one of the different sap5 operational modes and controls t he digital i/o ports accordingly. in slave mode , it processes the received master telegrams and computes t he contents of the slave answer if required. table 3 . 2 lists all master calls that are decoded by the sap5 in slave mode. to prevent the critical situation in which the sap5 becomes locked in a prohibited state ( e.g., due to exposure to strong electromagnetic radiation) , which could jeopardize the entire system, all prohibited states of the state machine will lead to an unconditioned logic reset which is comparable to the as- i call reset _ slave ( res ). 5.16. status registers table 5 . 21 shows the sap5 status register content. the use of status bits s0, s1 , and s3 is compliant with the as- interface complete specification . status bit s2 is not used. the status register content can be det ermined by use of a read_status ( rdst ) master request (refer to table 3 . 2 ). table 5 . 21 status register content status register bit sx = 0 sx = 1 s0 eeprom write accessible stored s lave a ddress volatile and/or eeprom access blocked (write in progress) 1) s1 n o p eriphery f ault detected ; eeprom firmware area and safety area c ontent consistent periphery fault detected; parity bit error in eeprom firmware area or safety area s2 static zero n/a s3 eeprom content consistent 2) eeprom contains corrupted data 2) 1) status b it s0 is set to ?1? as soon as a dela master request was rec eived and the slave address was not equal to ?0? before the request . i t is also set for the entire duration of each eeprom write access. 2) see section 4.2 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 46 january 28, 2016 5.17. communication monitor/watchdog the sap5 contains an independent communication monitor that observes the processing of data_exchange ( dexg ) and write_parameter ( wpar ) requests. if no such requests have been processed for more than 94.2ms (+4ms) the communication monitor recognizes a no data/parameter exchange status and turns the red status led ( i.e., led2) on. any subsequent data_exchange or write_parameter request w ill allow the communication monitor to start over and will turn the red status led off. the communication monitor is only activated for a slave addresses not equal to zero (0 hex ) and while the sap5 is processing the first write_parameter request after init ialization. it becomes deactivated at any sap5 r eset or after the reception of a delete_address r equest. activation of the communication watchdog depends on several eeprom flags and the parameter port p0 o utput r egister . note: the value of the parameter port p0 i nput does not have any influence on the communication w atchdog activation. only the master can change the activation status by sending a corresponding write_parameter ( wpar ) request. this allows using the feature even if io _ code = 7 is selected. in this case, the parameter port pins are mapped into data input pins. however, since the activation of the communication watchdog only depends on the value of the parameter output register, the watchdog functionality still remains controll ed by the master. watchdog activation through the value of the parameter port p0 is not available in safety mode. table 5 . 22 activation of the sap5 communication watchdog lock_ee_prg eeprom flag inhibit_watchdog eeprom flag p0_watchdog_activation eeprom flag safety_mode_ enable parameter port p0 o utput r eg ister watchdog activation 0 x x x x off 1 1 x x x off 1 0 0 x x on 1 0 1 1 x on 1 0 1 0 0 off 1 0 1 0 1 on the communication watchdog recognizes a no data exchange status if all of the following conditions are true: ? the communication watchdog is activated. ? no dexg or wpar request has been processed for more than 94.2ms (+4ms). ? slave address is not equal to zero (0 hex ). ? no eeprom write access is active.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 47 january 28, 2016 if the communication watchdog detects a no data exchange status, it takes the following actions: ? it concurrently generates the data and parameter strobe signals at the dstbn an d pstbn pins with timing according to figure 5 . 3 and figure 5 . 2 respectively. note: at this time, the dat a and parameter output values still comply with the values received with the last dexg and wpar master call, respectively. ? after the dstbn and pstbn strobe generation has finished, the communication watchdog invokes an unconditioned sap5 r eset. it sets the data_exchange_disable flag and afterwards starts the sap5 initialization procedure, switching all data and parameter outputs inactive. in order to resume normal data port communication after a watchdog sap5 reset , the data_exchange_disable flag must be cleared again. therefore, the master must send a wpar request again before the data port communication can be re - established. this ensures new parameter setup of any connected external circuitry. the state until the data_exchange_disable flag returns to ?0? is signaled by a certain led1 and led2 status indication (refer to section 5.11 ). 5.18. safety mode (sap5s only) the safety mode is active a s soon as the eeprom flag safety_mode_enable is set to ?1? (logic high ). thus, it is basically independent of the slave profile ; whereas the assignment of the 3 - level - input pins discussed below to either the data or parameter p ort depends on the io_code as described in table 5 . 15 . furthermore, in order to fulfill specific security requirements, the safety mode is not combinable with any of the followin g sap5 features: ? delay mode ( section 5.8.2 ) ? synchronous data i/o mode ( section 5.8.3 ) ? ext_addr_4i/4o_mode ( section 5.8.4 ) ? p0 watchdog activation ( section 5.17 ) the safety mode of the sap5 is of relevance to the actions following an dexg master request. instead of the regular input data provided at the data ports, a 4 - bit data word from a specific 8 ? 4 bit code table as described in the third - party document specification of safe as - i transmission (see section 9.2 ) is transmitted to the master. cycling the code table is used to transmit another data word with each dexg master call. in order to meet specif ic safety requirements , the data words transmitted to the master pass through a special pre - processing. therefore, the code table stored within the safety area of the eeprom (refer to table 4 . 4 ) does not match the referenc e code table as specified in the specification of safe as - i t ransmission but is derived from a special coding scheme as described in table 5 . 23. see the requirements below the table for the explanation of the asterisks in the table.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 48 january 28, 2016 table 5 . 23 example for cryptographic code table note: an asterisk (*) is used to indicate bits that have changed from the original bit. reference code table step 1 : c ycle d0/d2 by o ne c ycle step 2 : i nvert d0/d2 step 3: s wap d1 ? d3 code table w ritten to the eeprom d3 d2 d1 d0 d3 d2 d1 d0 d3 d2* d1 d0* d3* d2* d1* d0* swap_flag 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 0 0 0 0 1 0 0 0 1 0 0 1 1 0 0 0 1 1 0 1 1 0 1 1 0 0 1 1 0 0 1 1 1 0 0 1 0 0 1 1 0 0 1 0 1 1 1 0 1 0 1 1 1 1 1 0 1 1 1 0 0 1 0 1 1 1 1 1 0 1 0 1 1 1 0 1 1 1 1 1 0 0 1 1 0 1 1 0 0 0 0 0 1 0 1 0 1 1 1 0 0 1 1 0 1 1 0 0 1 1 0 0 the eeprom code table must be derived from a reference code table that meets the following requirements : 1. looking up in the reference code table, the data bit vectors d0 and d2 are scrolled forward by one cycle. refer to table 5 . 23 for an example. 2. data bit vectors d0 and d2 are inverted and stored as d0* and d2* in the eeprom . 3. four out of eight data bits from the vector d1 are interchanged with the respective data bits from vector d3. the respective bits are marked with swap_flag = ?1?. unchanged da ta bit pairs are marked with swap_flag = ?0?. coded in such a way, the vectors are stored as d1* and d3* in the eeprom . 4. the additional swap_flag attached to each data word is stored in the eeprom as well. running in safety mode , the eeprom data bits d0* an d d2* are put out at the port d1/d3 or p1/p3, respectively (for port configuration , refer to table 5 . 15) . an external circuit must invert these signals , which adds a voltage offset (refer to figure 5 . 8 ) and delays it for about 20 s. thus the data actually will be transmitted with the subsequent as - i cyc le. furthermore, the safety - related switches are connected between the external circuitry and the sap5 safety inputs f - d0* and f - d2* (refer to figure 5 . 7 ).
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 49 january 28, 2016 figure 5 . 7 safety mode data processing d2* f - d2* d0* inverting , offset1, delay inverting, offset2, delay f - d0* swap_flag i2 as - interface communication i0 i3 i1 d1* d3* offset2 f - d3* offset1 sap5 f - d1* i nformation stored in the e eprom the special input ports f - d0* and f - d2* act as 3 - level - input pins in safety mode . in order to ensure proper decoding of input data, the voltages must satisfy requirements as specified in below figure 5 . 8 and in table 5 . 5 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 50 january 28, 2016 figure 5 . 8 data input voltage constraints in safety mode as soon as the f - d0* input pad detects an offset level less than v ofl (max) , the sap5 resets the data input for d1 (f - d1*), signa ling an open state at the safety switch connected to d0*. the input data for d3 (f - d3*) will be reset if f - d2* detects an offset level less than v ofl (max ). provided that the offset levels are not missing, the e e prom bits d1* and d3* are transmitted as data bits d1 and d3 if swap_flag = ?0? ; otherwise they are swapped. in order to avoid desynchronization with the safety monitor in case the as - i master repeats a dexg call, the sap5 will not update the data code word for 224 s (+16 s) after a dexg call had been processed. 5.19. master and repeater mode s 5.19.1. master/ repeater mode activation the sap5 master/ repeater mode functionality is enabled via the master_mode eeprom flag (refer to table 4 . 2 ). in order to activate the master_mode , an sap5 reset ( see section 5.13 ) must be performed after programming the eeprom master_mode flag. for the distinction between master and repeater mode , the id_code can be set to a specific value as described in table 5 . 24 . note : the id_code must be programmed before activation of the master_mode flag. once the master_mode flag is set to logic high , the slave functio nality of the sap5 is no longer available, preventing any write access to the eeprom by use of as- i master requests as described in section 4.3 . moreover, the master and repeater mode functionality can be disabled generally by use of a hidden eeprom flag. this flag is inaccessible by the user, but can be set during the idt product ion test.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 51 january 28, 2016 table 5 . 24 activation of the sap5 master/repeater mode master_mode eeprom flag id_code master mode 1 master mode 2 repeater mode 0 x off off off 1 0 to 4 on off off 1 6 to f hex off on off 1 5 off off on 5.19.2. pin assignment in master and repeater modes in master and repeater mode , the sap5 pins are configured as follows. pins that are not used are kept at logic high (high impedance) state in order to reduce internal power dissipation of the sap5 . figure 5 . 9 sap package pin assignment in master/repeater mode resetn rx_dat osc2 osc1 not used not used not used tx_dat not used not used not used not used apf not used not used uout u5r ltgn cdc ltgp sap5 pin 1 table 5 . 25 sap5 pin assignment in master and repeater mode s sop 20 pin # so p 16 pin # name signal name pin c onfiguration description in master/repeater mode 1 - p1 none i/o not used 2 - p0 none i/o not used 3 1 d1 none i/o not used 4 2 d0 tx_dat in t ransmit signal (manchester ii signal) 5 3 dstbn resetn in e xternal reset input (active low) 6 4 led1 rx_dat out r eceive signal (manchester ii signal) 7 5 osc2 osc2 out crystal oscillator
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 52 january 28, 2016 sop 20 pin # so p 16 pin # name signal name pin c onfiguration description in master/repeater mode 8 6 osc1 osc1 in crystal oscillator / e xternal clock input 9 7 u5r u5r out regulated 5v power supply 10 8 ltgn ltgn in as-i transmitter/receiver output ; to be connected to asi - 11 9 ltgp ltgp in as-i transmitter/receiver input, to be connected to asi + via reverse polarity protection diode ; input for the power fail comparator 12 10 cdc cdc out external buffer capacito r 13 11 uout uout out decoupled actuator/sensor power supply 14 12 pfault none in not used 15 13 led2 none out not used 16 14 pstbn apf out as-i power fail signal 17 15 d3 none i/o n ot used 18 16 d2 none i/o n ot used 19 - p3 none i/o n ot used 20 - p2 none i/o n ot used 5.19.3. functional description in master/repeater mode , the sap5 provides a simple physical - layer interface function between the as - i line and an external binary channel . the signal rx_dat represents the manchester - ii- coded, re - synchronized equivalent of the telegram signal received at the as- i input channel. polarity of that bit stream depends on the programmed operation mode according to table 5 . 26. table 5 . 26 functional differences between sap5 master and repeater mode s modulation of s ignal rx_dat if as -i power fail s loopback mode polarity of signal rx_dat master mode 1 on on active high master mode 2 off on active high repeater mode off off active low every as - i telegram received is checked for consistency with the protocol specifications and timing jitters are removed if they are within the specified limits. if a telegram error is detected, the output signal becomes inactive for a time period defined by t break (refer to table 5 . 28). the signal tx_dat is directly forwarded to the as - i line transmitter avoiding any additional logic delays.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 53 january 28, 2016 if the loopback mode is not active, the as - i receiver is disabled while the sap5 is transmitting an as - i signal. otherwise, the transmitted signal is read back in parallel and provided at the rx_dat output for checkup purposes. the l oopback time t loopback is mainly defined by the analog signal processing within the receiver and the transmitter. however, an a dditional delay of up to 1875ns can be inserted if necessary. therefore, the id _code_extension_2 eeprom register must be programmed as described below. note : the id_code_extension_2 must be programmed before programming of the master_mode flag. once the ma ster_mode flag is set to logic high , the slave functionality of the sap5 is no longer available, preventing any write access to the eeprom by use of as- i master requests as described in section 4.3 . table 5 . 27 programmable variation of the loopback t ime id_code_extension_2 ( id2_bit3 to id2_bit0 ) ? t loopback 0000 0 0001 +125ns 0010 +250ns 0011 +375ns 0100 +500ns 0101 +625ns 0110 +750ns 0111 +875ns 1000 +1000ns 1001 +1125ns 1010 +1250ns 1011 +1375ns 1100 +1500ns 1101 +1625ns 1110 +1750ns 1111 +1875ns
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 54 january 28, 2016 in master/repeater mode , the sap5 provides an as - i power - fail detector. it consists of a comparator directly connected to the ltgp pin that generates a logic signal if the voltage at the ltgp pin drops below v apf (refer to table 5 . 28 ). a subsequent digital signal processing of the comparator output signal is performed as follows: ? an anti - bouncing filter removes any signal states shorter than 6 s. this is to eliminate the influence of as - i telegrams that are added onto the as- i dc voltage. ? an additional anti - bouncing filter with different filter times for activation and deactivation of the power - fail signal removes short power - fail pulses. ? the as- i power - fail signal is provided directly active high as the signal apf . ? additionally, in master mode , the as - i power - fail signal modulates the rx_dat signal ; whereas the active state is signaled by logic high level. table 5 . 28 master/repeater mode parameter parameter symbol min max unit loopback time in master mode 1) t loopback 4.9 6.5 s as-i power fail voltage threshold v apf 21.5 23.5 v minimum activation time for signaling of as-i power fail by use of the rx_dat signal 2) t apf_rx_dat 640 704 s release time of the as-i power fail state within the rx_dat signal 2) t apf_on_rx_dat 64 s minimum activation time for signaling of as-i power fail by use of the apf signal 2) t apf_apf 704 768 s as-i power fail hold time t hold_apf 64 s delay time after return of the as -i power t apf_off 64 128 s break time in case of an erroneous as-i signal t break 9 15 s 1) loopback time is the time difference between an edge in the man code of signal tx_dat and the corresponding edge in the manchester - code of the signal rx_dat. the voltage trigger level for measurement of the edge time is defined by v u5r /2. the actual loopba ck time may be adjusted by programming the id_code_extension_2 eeprom register as described in table 5 . 27. 2) in master mode, the as- i power fail state is already signaled by the rx_dat signal as soon as the power fail condition is true for a time more than t apf_rx_dat. however, in order to start the apf minimum hold state (t hold_apf ), the power fail condition must remain true for anothe r time period defined by t apf_on_rx_dat . otherwise, the rx_dat signal returns to its idle state (logic low) immediately.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 55 january 28, 2016 5.20. write protection of id_code_extension_1 the id_code_extension_1 register of the sap5 can either be manufacturer configurable or user configurable. as soon as the lock_ee_prg flag is set, access to the id_code_extension_1 is handled as follows: ? if the flag inhibit_write_id1 is set (?1?) in the firmware are a of the eepr om , id_code_extension_1 is manufacturer configurable (refer to table 4 . 2 ). ? in this case , the slave response to a read_id_code_1 ( rid1 ) request is constru cted out of the data stored on the internal eeprom address 2 in user area of the eeprom . ? it does not matter which data is stored in the id_code_extension_1 register in eeprom address 1 in the user area. the sap5 will always respond with the protected manuf acturer programmed value. ? there is one exception to this principle. if the sap5 is operated in extended address mode, b it 3 of the returned slave response is taken from the eeprom address 1 register in the user area. this is because b it 3 functions as the a/b slave selector bit in this case and must remain user configurable. ? to ensure consistency of the id_code_extension_1 stored in the data image of master as well as in the eeprom of the slave, the sap5 will not process a write_extended_id_code_1 request if the data sent does not match the data that is stored in the protected part of the id_code_extension_1 register. it will neither access the eeprom nor send a slave response in this case. ? note: as defined in the as - interface complete specification , a mod ification of the a/b slave selector bit must be performed bit selective. that means the as - i m aster must read the id_code_extension_1 first, modify bi t 3 , and send the new 4 - bit word that consists of the modified bit 3 and the unmodified b its 2 to 0 back t o the slave. ? if the inhibit_write_id1 flag is not set (?0?), id_code_extension_1 is completely user configurable. the data to construct the slave response to a read_id_code_1 request is completely taken from the id_code_extension_1 register on eeprom addre ss 1 in the user area. ? a write_extended_id_code_1 request will alway s be answered and initiate an ee prom write access procedure in this case. manufacturer configuration of the id_code_extension_1 register is only possible as long as the lock_ee_prg flag is not yet set. in this case, the write_extended_id_code_1 requ e st causes a write access that differs from the procedure described on page 20 . instead of the security_flag procedure, the id_code_extension_1 is written to both eeprom addresses 1 and 2 in the user area of the ee prom. this method of duplicate saving ensures data consistency even in the case of an accidental interruption of the e e prom write process during modification of bit 3 in extended address mode . refer to table 5 . 29 for an overview of the different programming and read out options of id_code _extension_1.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 56 january 28, 2016 table 5 . 29 write protection of id_code_extension_1 master call id_code lock_ee_prg inhibit_write_id1 reaction slave ans wer wid1 a hex 0 0 write id1_user + id1_manufacturer ( user area address 1 and 2) yes 1 new id1 matches id1_manufacturer : write id1_user + id1_manufacturer yes new id1 does not match id1_manufacturer : no action no 1 0 write id1_user yes 1 new id1 matches id1_manufacturer : write id1_user yes new id1 does not match id1_manufacturer : no action no a hex 0 0 write id1_user + id1_manufacturer yes 1 new id1[2:0] matches id1_manufacturer [2:0]: write id1_user + id1_manufacturer yes new id1[2:0] does not match id1_manufacturer [2:0]: no action no 1 0 write id1_user yes 1 new id1[2:0] matches id1_manufacturer [2:0]: write id1_user yes new id1[2:0] does not match id1_manufacturer [2:0]: no action no rid1 a hex 0 0 return id1_user yes 1 return id1_manufacturer 1 0 return id1_user 1 return id1_manufacturer a hex 0 0 return id1_user 1 return id1_user [3], id1_manufacturer [2:0] 1 0 return id1_user 1 return id1_user [3], id1_manufacturer [2:0] the slave answer to a write_id_code1 requ e st is ?0? in any case as specified in table 3 . 2 .
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 57 january 28, 2016 6 application circuits the following figures show typical applica tion cases of the sap5. n ote that these schematics show only basic circuits principle s . for more detailed application information , see the separate sap51/sap5s application notes document. figure 6 . 1 outlines a standard slave application circuit. figure 6 . 2 shows a safety mode application circuit. a master mode application is shown i n figure 6 . 3 . figure 6 . 1 standard application circuit, directio n of data i/o depends on io_code sap 51 / sap 5 s 5 . 33 / 16 mhz 1 n 4001 zmm 39 100 nf 10 f 100 nf asi + asi - osc 1 osc 2 ltgp cdc ltgn led 2 led 1 pstbn p 3 p 2 p 1 p 0 dstbn d 3 d 2 d 1 d 0 pfault u 5 r uout 100 nf d 3 d 2 d 1 d 0 p 3 p 2 p 1 p 0 0 v + 24 v pstbn dstbn pfault
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 58 january 28, 2016 for the circuit shown in figure 6 . 2 , r1 and c1 form a low - pass - filter for the delay of the output of the sap5 for about 20 s. the transistor performs the inversion; the voltage divider r2/r3 shift s the low level in the range of 1.5v to 2.5v. the high level is provided from the pin?s pull - up feature. figure 6 . 2 safety mode application sap 5 s 5 . 33 / 16 mhz 1 n 4001 zmm 39 100 nf 10 f 100 nf asi + asi - osc 1 osc 2 ltgp cdc ltgn d 3 d 2 d 1 d 0 u 5 r uout 100 nf 0 v + 24 v + 5 v
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 59 january 28, 2016 figure 6 . 3 sap5 master mode application u_ext send receive /power_fail gnd_ext +ub vo gnd +ub vo gnd +ub vo gnd sap5 5.33/ 16mhz 1n 4001 zmm 39 100nf asi+ asi- osc1 osc2 ltgp cdc ltgn led2 led1 pstbn/apf p0 p1 p2 p3 dstbn /resetn d0 d1 d2 d3 u5r uout 10f 100nf +ub vo gnd /reset
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 60 january 28, 2016 7 package specifications 7.1. package pin assignment table 7 . 1 sap51 / sap5s package pin list sop 20 pin sop 16 pin name direction type description 1 - p1 i/o pull -up / o pen-d rain (*) parameter p ort p1 / data i nput port 1 if io_ config = 7 2 - p0 i/o pull -up / o pen-d rain (*) parameter p ort p0 / data input port 0 if io_config = 7 3 1 d1 i/o pull -up / o pen-d rain data p ort d2 4 2 d0 i/o pull - up / open-d rain data p ort d0 5 3 dstbn i/o pull -up / o pen-d rain data strobe o utput / reset i nput 6 4 led1 out open -d rain led 1 status indication 7 5 osc2 out analog (5v) crystal o scillator 8 6 osc1 in analog / cmos (5v) crystal o scillator / external c lock i nput 9 7 u5r out analog regulated 5v power supply 10 8 ltgn in analog / supply as-i transmitter/receiver output; to be connected to asi - 11 9 ltgp in analog / supply as-i transmitter/receiver input; to be connected to asi + via reverse polarity protection diode 12 10 cdc out analog external buffer capacitor 13 11 uout out analog decoupled actuator/sensor power supply 14 12 pfault in pull -up periphery fault input (l ow = periphery fault) 15 13 led2 out open d rain led 2 status indication 16 14 pstbn i/o pull -up / o pen-d rain parameter strobe output 17 15 d3 i/o pull - up / open-d rain data port d3 18 16 d2 i/o pull - up / open-d rain data port d2 19 - p3 i/o pull - up / open-d rain (*) parameter port p3 / data input port 3 if io_config = 7 20 - p2 i/o pull - up / open-d rain (*) parameter port p2 / data input port 2 if io _ config = 7 (*) the pull - up current source on these parameter ports is switched off if the slave device is programmed with i/o configuration code 7 and a dexg master call is processed. all open - drain outputs are nmos - based. pull - up properties at input stages are achieved by current sources refer enced to u5r.
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 61 january 28, 2016 figure 7 . 1 sap51 / sap5s sop20 package pin assignment p1 p0 p2 p3 pin 1 sap51 sap5s d2 d3 pstbn led2 pfault uout cdc ltgp dstbn led1 osc2 osc1 d1 d0 u5r ltgn figure 7 . 2 sap51 / sap5s sop16 package pin assignment dstbn led 1 osc 2 osc 1 d 1 d 0 d 2 d 3 pstbn led 2 pfault uout u 5 r ltgn cdc ltgp sap 51 sap 5 s pin 1
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 62 january 28, 2016 7.2. sop 16 (300 mil) package outline the sap51 / sap5s is available in a 16- pin sop package. its dimensions are given in figure 7 . 3 and table 7 . 2 . figure 7 . 3 sop 16 package outline dimensions table 7 . 2 sop 16 package dimensions (mm) symbol a a 1 a 2 b p c e d e h e k l p z nominal 1.27 minimum 2.35 0.10 2.25 0.35 0.23 1 0 . 21 7.40 10.00 0.25 0. 61 0 maximum 2.65 0.30 2.45 0.49 0.32 1 0 . 46 7.60 10.65 0. 79 8
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 63 january 28, 2016 7.3. sop 20 (300 mil) package outline the sap51 / sap5s is available in a 20 - pin sop package. the dimensions are given in figure 7 . 4 and table 7 . 3 . figure 7 . 4 sop2 0 package outline dimensions table 7 . 3 sop2 0 package dimensions (mm) symbol a a 1 a 2 b p c e d e h e k l p z nominal 1 . 27 minimum 2.35 0.10 2.25 0.35 0.23 12.60 7.40 10.00 0.25 0.40 0 maximum 2.65 0.30 2.45 0.49 0.32 13.00 7.60 10.65 0.81 8
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 64 january 28, 2016 7.4. package marking figure 7 . 5 package marking 20 - pin v ersion pin 1 top view bottom view pin 1 llllll ppppp - a zmd i d - xxxxyzz + g1 figure 7 . 6 package marking 16 - pin v ersion pin 1 top view bottom view pin 1 llllll + ppppp - b zmd i d - xxxxyzz g1 top marking: ppp pp - a product name sop20 package ppppp - b product name sop16 package zmdi manufacturer d revision code yyww date code (year and week) l assembly location zz traceability code bottom marking: llllll idt lot number
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 65 january 28, 2016 8 ordering information ordering code operating temperature package type rohs? packaging sap5sd - a - g1 - t - 25c to +85c sop20 / 300 mil yes tubes (37 parts/tube) sap51d - a - g1 - t sap5sd - a - g1 - r - 25c to +85c sop20 / 300 mil yes tape and reel (1000 parts/reel) sap51d - a - g1 - r sap5sd - b - g1 - t - 25c to +85c sop16 / 300 mil yes tubes (46 parts/tube) sap51d - b - g1 - t sap5sd - b - g1 - r - 25c to +85c sop16 / 300 mil yes tape and reel (1000 parts/reel) sap51d - b - g1 - r 9 related documents 9.1. related idt documents document sap5 /sap5s feature sheet sap51/sap5s application notes * sap51/sap5s release note rev d sap51/sap5s errata sheet management regulation: 0410 product development procedure ** process specification: idt c7d 0.6m technology ** visit the sap5s/sap51 web page at http://www.idt.com/products/as - interface/sap5 or contact your nearest sales office for the latest version of these documents. * documents marked with an asterisk (*) require a free customer login for access. ** documents marked with two asterisks (**) are available only on request. 9.2. related third - party documents document related web site as- interface complete spe cification version 3.0 rev5, 11.12 .20 13 www.as - interface.net specification of safe as - i t ransmission v2.01 , 12.05.2000 www.as - interface.net
sap51 / sap5s datasheet ? 2016 integrated device technology, inc. 66 january 28, 2016 10 glossary term description as-i actuator sensor interface plc programmable logic controller pll phase - lock loop uart universal asynchronous receiver/transmitter 11 document revision history revision date description 1.00 september 13 , 2005 first release. 2 . 0 0 march 21 , 200 7 ic revision c introduced 2. 1 0 april 2, 20 07 update o rdering i nformation 2.20 april 11 , 20 08 update to jedec - 020d 3.00 march 20, 2011 new template and minor changes . 3.10 july 17 , 201 2 ic revision d added 3 . 2 0 june 1 7 , 201 5 new template applied . update for contact information. addition of definitions for absolute maximum ratings and operating conditions for section 2 . correction of references to uin and dsr pin s, which ar e not applicable. revisions for formatting . minor edits for clarity. january 2 8 , 2016 changed to idt branding. corporate headquarters 6024 silver creek valley road san jose, ca 95138 www.idt.com sales 1- 800- 345- 7015 or 408 - 284- 8200 fax: 408 - 284- 2775 www.idt.com/go/sales tech support www.idt.com/go/support disclaimer integrated device technology, inc. (idt) reserves the right to modify the products and/or specifications described herein at any time, without notice, at idt's sole d iscretion. performance specifications and operating parameters of the described products are determined in an independent state and are not guaranteed to perform the same way when installed in customer products. the information contained herein is provided without representation or warranty of any kind, whether express or implied, includin g, but not limited to, the suitability of idt' s products for any particular purpose, an implied warranty of merchantability, or non - infringement of the intellectual property rights of others. this document is presented only as a guide and does not convey an y license under intellectual property rights of idt or any third parties. idt's products are not intended for use in applications involving extreme environmental conditions or in life support systems or similar devices where the failure or malfunction of an idt product can be reasonably expected to significantly affect the health or safety of users. anyone using an idt product in such a manner does so at their own risk, a bsent an express, written agreement by idt. integrated device technology, idt and the idt logo are trademarks or registered tradem arks of idt and its subsidiaries in the united states and other countries. other trademarks used herein are the property of idt or their respective third party owners. for datasheet type definitions and a glossary of common terms, visit www.idt.com/go/glossary . all contents of this document are copyright of integrated device technology, inc. all rights reserved.


▲Up To Search▲   

 
Price & Availability of SAP51D-A-G1-T

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X